Skip to content

generator naming conventions #99

Description

@jonschlinkert

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions