Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Initialize a new branch for a new UX #17

Closed
lbroudoux opened this issue May 26, 2024 · 2 comments
Closed

Initialize a new branch for a new UX #17

lbroudoux opened this issue May 26, 2024 · 2 comments
Assignees
Labels
component/api kind/enhancement Enhancement of existing feature kind/task
Milestone

Comments

@lbroudoux
Copy link
Member

lbroudoux commented May 26, 2024

We'd like to test new UX frontend for Hub with modern techno and ability to be reused as a web component.

  • Initialize a new-ux branch
  • Update server backend dependencies to latest versions
  • Do some house-keeping by updating the license headers
@lbroudoux lbroudoux self-assigned this May 26, 2024
@lbroudoux lbroudoux added component/api kind/enhancement Enhancement of existing feature kind/task labels May 26, 2024
@lbroudoux lbroudoux added this to the 0.2.0 milestone May 26, 2024
lbroudoux added a commit that referenced this issue May 26, 2024
Signed-off-by: Laurent Broudoux <laurent.broudoux@gmail.com>
soGit added a commit to soGit/hub.microcks.io that referenced this issue Jul 10, 2024
soGit added a commit to soGit/hub.microcks.io that referenced this issue Jul 10, 2024
Signed-off-by: soGit <soroka.sergei@gmail.com>
soGit added a commit to soGit/hub.microcks.io that referenced this issue Aug 15, 2024
Signed-off-by: soGit <soroka.sergei@gmail.com>
@soGit
Copy link
Contributor

soGit commented Aug 19, 2024

Hello @lbroudoux, I like your idea to start from hub.microcks.io
I propose to focus on the Frontend folder first (because the main point is to develop an migration approach for Microck's FrontEnd related projects). To move iteratively, let start with updating dependencies to the lates minor versions (check PR #24 )
after that, I want to introduce "prettier" so, we have consistently formatted code across the project.
Along that we need to define the core functionality, so hight level e2e test can be created to avoid manual checks and simplify refactoring. https://playwright.dev/ can be used.
After that, migrate to the latest angular. If any lib(s) is not supported (migrate to https://shoelace.style/ or https://material.angular.io/components/categories).

Once we are up to date, we might switch to https://astro.build/ because hub.microcks.io has a mostly static content, that can be prerendered.

What to you think?

Copy link

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale State due to inactivity label Sep 21, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 21, 2024
@lbroudoux lbroudoux removed the stale State due to inactivity label Oct 21, 2024
@lbroudoux lbroudoux modified the milestones: 0.2.0, 0.3.0 Oct 21, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
component/api kind/enhancement Enhancement of existing feature kind/task
Projects
None yet
Development

No branches or pull requests

2 participants