-
Notifications
You must be signed in to change notification settings - Fork 55
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
(Feature) Module bundles or Partial modules #175
Labels
enhancement
New feature or request
Comments
skejeton
changed the title
(Feature) Partial modules
(Feature) Module bundles / Partial modules
Jun 29, 2022
skejeton
changed the title
(Feature) Module bundles / Partial modules
(Feature) Module bundles or Partial modules
Jun 29, 2022
@skejeton I think it will be difficult for a user to distinguish between |
I agree, import "ui/*" does sound pretty nice |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometimes modules can get quite big, and it makes sense to separate them. Sometimes modules can just be bundles of other modules.
In my case the UI module handles many different things, and keeping it all in one file is pretty inconvenient.
The idea is that you are able to "load" a module into the module itself. This essentially puts the loaded modules to the root (the module that loads) modules namespace. This is preferably not a text substitution to retain compatibility between bundle included and standalone modules.
This also relates to #173 because this would essentially solve the problem by allowing you to wrap the conflicting modules into a bundle. (Mind you, this feature is just another feature in the bucket of ideas, these problems can be addressed one way or another)
The text was updated successfully, but these errors were encountered: