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

Categorization of command-line generators #202

Open
clement-estone opened this issue Mar 1, 2022 · 3 comments
Open

Categorization of command-line generators #202

clement-estone opened this issue Mar 1, 2022 · 3 comments

Comments

@clement-estone
Copy link
Contributor

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:

image

And:

image

Wouldn't it be better to merge these categories as a single one (name TBD).

What do you think?

@jmcdo29
Copy link
Member

jmcdo29 commented Mar 1, 2022

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

@clement-estone
Copy link
Contributor Author

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.

@micalevisk
Copy link
Member

@clement-estone feel free to open a PR so we could see the final result

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

3 participants