Skip to content

Best Practice Recommendations for Angular App Structure #175

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mrzepinski opened this issue Apr 13, 2014 · 3 comments
Closed

Best Practice Recommendations for Angular App Structure #175

mrzepinski opened this issue Apr 13, 2014 · 3 comments

Comments

@mrzepinski
Copy link
Contributor

https://docs.google.com/document/d/1XXMvReO8-Awi1EZXAXS4PzDzdNvV6pGcuaF4Q9821Es/pub

.. and what do you think? :) I use it in my projects and it is much better, than default.

@DaftMonk
Copy link
Member

Definitely planning to implement this next. I want to do it as part of moving the sub generators into their own generator, and use a yo-rc.json file to keep track of the configuration for the project. Generator angular fullstack would scaffold the config file with some defaults for the separate angular module generator.

Example configuration:

<generator name>: {
  preprocessors: {
    script: 'js',                  // support for 'coffee'
    markup: 'html'                 // support for 'jade'
  },
  paths: {
    app: 'app.js',                 // where to automatically add routes
    components: 'app/components'   // uses googles angular project guidelines
  },
  templates: {                     // possibly allow people to replace some of the default templates with their own
    directive: 'my/custom/directive/',
    directiveTest: 'my/custom/directiveTest/'
  },
  regex: {},                       // possibly include some regex variables for configuring how routes are added
  prompts: {}                      
}

@DaftMonk
Copy link
Member

Have a look at the new structure here: #192

@mrzepinski
Copy link
Contributor Author

@DaftMonk sorry for my late :) It's look good. I can't wait next version. Any help is needed here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants