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
In an Angular Nation discussion today, it came up that it can be difficult to discover schematics due to the lack of a centralized registry. The closest things that exists are probably NPM and GitHub, which tend to be tagged "schematics" by convention, which is not intuitive to look for. The lack of discoverability makes it harder for user schematics to find their users beyond simple word of mouth.
Describe the solution you'd like
We should consider some kind of search functionality (either within the Angular CLI ng add --search or something in schematics directly) which looks for compatible packages on NPM. "Compatible" packages could be identified by inspecting the contents for the relevant JSON files or just looking for a "schematics" tag. Using a specific tag in the CLI could also help the community standardize on a particular convention to improve consistency. This could help improve discoverability of schematics.
Describe alternatives you've considered
The most obvious workaround is to search for schematics via your favorite search engine or directly on NPM. These are reasonable approaches, but will vary wildly in quality and may not be obvious to many devs who may not know what tags to search for.
The text was updated successfully, but these errors were encountered:
🚀 Feature request
Command (mark with an
x
)Description
In an Angular Nation discussion today, it came up that it can be difficult to discover schematics due to the lack of a centralized registry. The closest things that exists are probably NPM and GitHub, which tend to be tagged "schematics" by convention, which is not intuitive to look for. The lack of discoverability makes it harder for user schematics to find their users beyond simple word of mouth.
Describe the solution you'd like
We should consider some kind of search functionality (either within the Angular CLI
ng add --search
or something inschematics
directly) which looks for compatible packages on NPM. "Compatible" packages could be identified by inspecting the contents for the relevant JSON files or just looking for a "schematics" tag. Using a specific tag in the CLI could also help the community standardize on a particular convention to improve consistency. This could help improve discoverability of schematics.Describe alternatives you've considered
The most obvious workaround is to search for schematics via your favorite search engine or directly on NPM. These are reasonable approaches, but will vary wildly in quality and may not be obvious to many devs who may not know what tags to search for.
The text was updated successfully, but these errors were encountered: