yeoman init output #567

Closed
chrixian opened this Issue Sep 30, 2012 · 4 comments

Comments

Projects
None yet
3 participants

as you know, yeoman init executes a generator-- even if no generator is specified the result of yeoman init is really yeoman init yeoman:app.

the initial text output by yeoman init comes from the yeoman init grunt task not the generator that's ultimately used, which would be fine if it was a single line informing the user that yeoman is about to do whatever it was asked to do but it's not, it's 21 lines of text that (more than likely) doesn't apply to the generator you're about to run.

it tells me it's going to ask some questions and instructions how to answer them when my task may or may not ask any questions at all; then after a bunch of blank lines and ascii art, it informs me HTML5 Boilerplate, jQuery and Modernizr are included (again possibly having nothing to do with the ultimate task)

all this pre-generator output seems to jive with what yeoman init does with no arguments so i propose moving all that to the yeoman:app generator and replacing it with something short(er) and generator agnostic.

lastly, to illustrate my point open the terminal and run yeoman init with an invalid or misspelled generator name i.e. yeoman init icantspell ... the error message the user cares about is in there somewhere.

Owner

addyosmani commented Oct 4, 2012

all this pre-generator output seems to jive with what yeoman init does with no arguments so i propose moving all that to the yeoman:app generator and replacing it with something short(er) and generator agnostic.

I mostly agree with this. It doesn't make sense to display the artwork and additional lines unless a user has just started yeoman up and we want to make sure that the text shown makes sense in context. Perhaps the default text about H5BP and Modernizr etc. should be removed.

Contributor

btford commented Oct 8, 2012

+1; I'll get cracking on it when I have time. @addyosmani, do you have any advice on how to go about this?

addyosmani referenced this issue in yeoman/generator Oct 10, 2012

Closed

yeoman init output #89

Owner

addyosmani commented Oct 10, 2012

Agreed that we should solve this. @btford it would be done in the yeoman generator in the generators repo I believe. I've created https://github.com/yeoman/generators/issues/89 so we can track it.

addyosmani closed this Oct 10, 2012

Contributor

btford commented Oct 10, 2012

Actually, some of this lives in cli/tasks/init/yeoman.js in Yeoman itself. I'm going to submit a PR soon to both Yeoman and its Generators to hopefully make sense of this.

@btford btford added a commit to btford/yeoman that referenced this issue Oct 10, 2012

@btford btford Move yeoman ascii art and verbose intro out of yeoman init and into t…
…he generator space. Fixes #567
0703e6d

@szinya szinya pushed a commit to menthainternet/yeoman that referenced this issue Sep 17, 2014

@btford btford Move yeoman ascii art and verbose intro out of yeoman init and into t…
…he generator space. Fixes #567
909a3d7

@btford btford added a commit that referenced this issue Apr 24, 2015

@btford btford Move yeoman ascii art and verbose intro out of yeoman init and into t…
…he generator space. Fixes #567
45e2401
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment