Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Move the workspace to a standalone component architecture #823

Open
rgoj opened this issue May 7, 2023 · 0 comments
Open

Move the workspace to a standalone component architecture #823

rgoj opened this issue May 7, 2023 · 0 comments

Comments

@rgoj
Copy link
Collaborator

rgoj commented May 7, 2023

This work is part of #822 - see that issue for an overview.

The Angular world has been quickly moving towards a module-less standalone component architecture. In #818 I run the basic migration. One of the benefits I've already seen in Maptio is faster compilation times due to more granularity.

There's still a way to go to complete the change, here's a stab at a working list:

  • move the workspace to routing using lazy-loaded components
  • remove the workspace module file

The changes in the workspace module should hopefully serve as a blueprint for changes in the rest of the app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant