Generator Roadmap

[eddiemonge]

In an effort to be more transparent about the project, we are creating roadmaps for everything. This is the tentative roadmap for the Angular generator.

Priority 1

• Refactor all the tests to test everything, including all existing options
• Make everything configurable. This will include a combination of flags, prompts and a configuration file
  • File casing in both scripts and filenames
  • Paths to where things are located tip
  • Preprocessors declaration
• Support the project as a sub-generator for other projects (Angular full stack, MEAN stack, etc). This should happen as a side-effect of making everything configurable.
• Different organization of files. This includes the by module (proposed AngularJS team recommendation), or by function (current). Also where assets go in dev mode (CSS, JS, HTML)

Priority 2

• Remove minsafe files. Done
• Consolidate all template files/folders into a central location Done
• Add gulp as a build tool
• Add support for JS templates (adding grunt-angular-templates to the build tasks #277)
• Add Protractor E2E tests and templates
• Add option for UI-Router

Priority 3

• Add support for TypeScript (Typescript support for generator-angular #313, Adding typescript support to generator-angular #539)
• Add support for BabelJS
• Add support for Stylus, Less
• Add support for Jade (feat(build): add Jade support #420)
• Remove heavy reliance on Bootstrap so other frameworks can be used (maybe as a prompt choice)
• Make vanilla CSS (no framework selected) more visually appealing
• Add ESLint to the project (probably replaces JSHint)

Priority 4

• Support for backend implementations, whether that be proxies, rewrite rules, make it more composable for other generators or actually adding a backend REST server (highly unlikely though)
• uncss? remove css styles

If you think there are other things that should be added to the roadmap, or have questions about any of these, please feel free to comment.

[btford]

👍

[intellix]

Add support for JS templates = something like html2js? I was looking at this earlier. Was wondering how to integrate it into the usemin process and it seems like it involves creating a custom "flow" which would merge the templates.js from html2js into the concatinated script generated from the usemin block files.

[passy]

Excellent! 👍

@passy - from his phone
On Jan 20, 2014 8:00 PM, "Eddie Monge" notifications@github.com wrote:

In an effort to be more transparent about the project, we are creating
roadmaps for everything. This is the tenative roadmap for the Angular
generator.
Priority 1

• Refactor all the tests to test everything, including all existing
  options
• Make everything configurable. This will include a combination of
  flags, prompts and a configuration file (yo-rc.json)

Priority 2

• Remove minsafe files
• Consolidate all template files/folders into a central location
• Add support for JS templates

Priority 3

• Add support for TypeScript
• Add support for Stylus, Less
• Add support for Jade
• Remove Bootstrap from the project (cause a lot of issues but is
  open for discussion/debate)

If you think there are other things that should be added to the roadmap,
or have questions about any of these, please feel free to comment

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/553
.

[addyosmani]

👍 this looks sharp. Nice work putting this together @eddiemonge.

[jjt]

Bootstrap could be considered orthogonal to the generator, but I think it's better to leave it as the default option.

The Bootstrapped version makes gen-ng look like it's done a much better job than than the plain version, because it looks more like an actual website. I think that users who are new to gen-ng will be more impressed with the BS version and you'll have a higher adoption rate, while veteran users will (hopefully) know what they want and can choose to not install BS.

[eddiemonge]

@jjt The vanilla CSS version needs work. I updated the P3 with a better alternative

[jjt]

@eddiemonge Ah, nice! Was going to say that other frameworks would be a good addition, but didn't want to pile more on. As to a vanilla css look, including normalize.css, centering .content, and making the nav menu inline with no discs would go a long way.

[programbo]

I'd really like to see ui-router an an option. I'm know I'm not alone in preferring ui-router as my go-to over the default ngRouter. Also, I'll second that html2js request, and what ever became of that massive discussion about feature grouping (ngBoilerplate style) vs layer grouping?

[diwa-zz]

+1 for feature grouping

[ahimta]

+1 for jade or anything that makes writing HTML more developer friendly. I really don't like HTML syntax (writing opening and closing tag), I prefer HAML.

[34r7h]

Does "Support the project as a sub-generator for other projects" mean having the ability to generate sub-modules for larger projects, which are then thankfully separated by feature?

[vincivince]

+1 for Jade

[vincivince]

• Jade
• i18n
• html2js

-> grunt-jade-i18n + grunt-html2js

[ProLoser]

Any thoughts on adding proper module structure? Creating controllers/services/directives into respective directories seems like it is encouraging a now-considered poorer practice.