bandwidth / generator-incubator Goto Github PK

The auto-generated manifest does not use JSON "pretty printing" so it is difficult to read/maintain.

Add a readme to a project that contains several things

• project title
• build pipeline information
• license reference
• DavidDM badges

As a user I want the travis sub-generator to prompt me with a question like the following:

Select build artifacts that you would like to persist to Amazon S3:
[ ] npm-debug.log
[ ] some other artifact..

If I decided to persist any artifacts, then I should be prompted for S3 credentials, bucket to store in, etc.

To me, this sub-generator would simply add commands to be run in the after_script portion of the .travis.yml file. The commands that are added would use some helper scripts that are either added to the .travis.yml or are in some directory like .build.

The generator installs a lot of node dependencies when setting up a new project but none of them are added to package.json. This leaves the developer needing to manually set these up.

Prompt defaults like which NPM registry to publish to should be located in a JSON/YAML file somewhere so that individuals other than Bandwidth Incubator can use this project effectively.

_.extend() overwrites existing options _.defaults() is probably a better choice for JSHint overrides.

As a developer, I want to be able to use a generator-incubator sub-generator to put in place boilerplate code (grunt tasks, etc) for using RAML to document a REST API.

Currently, when installing the generator from NPM the main generator does not work. It prints out the welcome message in a loop and errors out. Even with this not working it is possible to run each of the sub-generators manually:

• yo incubator:core
• yo incubator:travis

The yo incubator command just prints a greeting message and delegates to all default sub-generators for incubator projects.

steps to recreate:
yo incubator
take default project name
type description then try to erase character. Instead of deleting one character it moves the cursor up multiple lines and makes it difficult to tell what has been deleted.

Currently .gitattributes causes line endings to be normalized in a platform-specific way. This causes problems for JSCS on windows. See inetCatapult/shortwave#7

As a generator-incubator dev I would like for helper and utility scripts used in a build to have a place to live other than inside the .travis.yml file. This would make it so that only project specific information is in the .travis.yml file. Anything in the .build directory is placed there if and only if a feature is requested, like build artifact persistence, while generating a project.