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
The Awesome NestJS list contains several command-line tools used to generate code automatically. They are however divided in multiple categories, which can lead to confusion, such as:
And:
Wouldn't it be better to merge these categories as a single one (name TBD).
What do you think?
The text was updated successfully, but these errors were encountered:
I'm not sure they should be merged. The Command Line / Terminal section refers to either generators (like the CLI and Yeoman Generator) and CLI creators (like nest-commander and NestJS Console). I think the Typescript SDK Generator and Nestia achieve the same goal (creating an SDK from a NestJS application), so maybe we should create an SDK section, but these shouldn't be merged in general in my opinion.
Perhaps we could make a Schematics / Generation section for the Nest CLI and Yeoman Generator (plus any community schematics) and make it clearer that the Command Line / Terminal section is for creating command line applications
Perhaps we could make a Schematics / Generation section for the Nest CLI and Yeoman Generator (plus any community schematics) and make it clearer that the Command Line / Terminal section is for creating command line applications
That's what I meant, sorry if it wasn't clear. A new section is what I had in mind, to group all generators in one place.
The Awesome NestJS list contains several command-line tools used to generate code automatically. They are however divided in multiple categories, which can lead to confusion, such as:
And:
Wouldn't it be better to merge these categories as a single one (name TBD).
What do you think?
The text was updated successfully, but these errors were encountered: