ember help generate

[jgwhite]

$ ember help generate
ember generate <blueprint> <options...>
  Generates new code from blueprints
  aliases: g
  --dry-run (Default: false)
  --verbose (Default: false)

  Available blueprints:
    my-app:
      foo
      bar
    ember-cli:
      acceptance-test
      adapter
      api-stub
      app
      blueprint
      component
      controller
      helper
      initializer
      mixin
      model
      resource
      route
      serializer
      service
      template
      transform
      util
      view

[rwjblue]

Definitely 👍.

I would love to see the same output from ember help generate, but I think that will take a bit of refactoring of the help command which could be part of another PR.

[stefanpenner]

RebAse

[stefanpenner]

So why add list. When help is already present?

[jgwhite]

@stefanpenner seemed like it would take a little refactoring to get it into help, and that this would be the most expedient why to provide these docs. Aiming to integrate with help eventually.

[stefanpenner]

i would prefer to hold of an interim feature like this, if it will be entirely replaced with help in the future. I fear adding/removing flags is a great way to confuse people.

[jgwhite]

@stefanpenner cool. I'll push ahead integrating it with help.

[stefanpenner]

cc @njj023

[jgwhite]

@stefanpenner @rjackson this is ready for another pass.

Refactored printUsageInstructions into printBasicHelp and printDetailedHelp.

Not tied to the naming of those methods, though it seems appropriate they match up with the help command. Should they be basicHelp and detailedHelp and return documentation strings rather then doing the printing themselves?

[rwjblue]

Looks good. I like the name change (makes it much clearer what each thing does).

👍

[rwjblue]

This got me thinking: should a blueprint also have the ability to print information? I'm thinking that a blueprint named easyForm or validations may not actually be descriptive enough (or provide information on the requirements). Perhaps the Blueprint.list function could be extended to instantiate the blueprint, and call the printBasicHelp on each (which could be listed alongside the name).

I do not think that this proposal should block this PR though. I think this is absolutely a step in the right direction, and I'd like this available in the next release. Then as we have time, we can add the blueprint level printouts.

[jgwhite]

@rjackson been thinking exactly the same.

$ ember help generate
ember-cli:
  model <attr:type...>
  route <type:(resource|route)>
  ...

[rwjblue]

Yes, exactly! But I think that could be a second PR building on this one (so as not to hold this up from the next release), unless of course you disagree and want to tackle it here...

[jgwhite]

Let’s add it in a second PR.

[rwjblue]

Sadly, due to CHANGELOG shenanigans this will need to be rebased.

[jgwhite]

Rebased.

[rwjblue]

Travis is not happy, and I'm pretty sure it's because this needs to be updated (due to the rename from integration to acceptance).

[jgwhite]

Whoops! Forgot about that. Should be good now.

[stefanpenner]

this is awesome!!