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

generator naming conventions #99

Open
jonschlinkert opened this issue Jul 6, 2016 · 2 comments
Open

generator naming conventions #99

jonschlinkert opened this issue Jul 6, 2016 · 2 comments

Comments

@jonschlinkert
Copy link
Member

I'm about to release verb 0.9.0, and before I do I think we should change generator naming conventions, and if we do, now is the time to do it since we only have one generator published: verb-readme-generator.

Now that generate and update are released, it seems clear that the naming convention should be verb-generate-*, instead of verb-*-generator, which mirrors the naming conventions of generate and update.

This way, generate can continue to focus on "micro-generators" that can be used as plugins in other generators, and verb, assemble or update can build on those.

For example, we could use generate-foo as a base for:

  • verb-generate-foo
  • assemble-generate-foo

and so on.

I propose we:

  • rename this lib
  • publish verb-generate-readme to npm
  • add a deprecation notice to verb-readme-generator to redirect users to the new name

thoughts?

@doowb
Copy link
Member

doowb commented Jul 6, 2016

I like the app-generate-* convention.

@tunnckoCore
Copy link

A lil lately but me too. :D 👍

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