You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 3, 2023. It is now read-only.
This wasn't meant to be just the "ng" prefix, but any prefix. At the moment, I'm leaning toward not including this feature as the rules for mapping names to files is getting very complex already.
I think that the problem has several other roots - the original curvature of naming units in angular. Instead of calling the modules they use sophisticated forms ngroute / sanitize...
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Quite often, module names have a vendor prefix which doesn't relate to the filesystem directly, but could be aliased to a certain directory.
e.g. ngResource could alias the "ng" part to "lib/angular-"
The text was updated successfully, but these errors were encountered: