Core contributors about generator-ng-fullstack HOT 13 CLOSED

I would like to start talking about the following topics:

• directory structure (e.g. server & client clear separation, naming conventions, no duplicate names)
• coding best practices (e.g. based on https://github.com/johnpapa/angular-styleguide)
• gulp (core task, split configuration in several files, best practices)

We should open issues for theses topic and fix them before starting more complex tasks.

from generator-ng-fullstack.

Gulp task issue is right here

@jgodi said he'd give a hand with the best practices based on jhon papa's styleguides.

About the directory structure, do you see something that should be changed or do you mean to document the way modifications should be made? Or both?

Also, I agree about making it more solid before going crazy.

from generator-ng-fullstack.

Yes, I will comb through the client side code and get it up to terms with the style guide. Should be done soon :)

I do agree that splitting of the gulp tasks would be nice. More so, I would like to see a gulp.config.js where all the paths/files/settings are defined that are pulled into the gulp tasks. That way users have a one stop shop to change config rather then hunting down into task files.

from generator-ng-fullstack.

About the directory structure, do you see something that should be changed or do you mean to document the way modifications should be made? Or both?

I created a separated issue about this topic: #15 (Directory structure)

from generator-ng-fullstack.

Alright, just created the organization: nxgen.

Nothing there yet, just waiting on who's willing to contribute so I can add you there and move this repo.

😄

from generator-ng-fullstack.

Perfect. When I get more free time I will be a regular contributor :)

It would be nice to maybe make a way to opt-out of the server creation. For those people at companies (like me) who would love the front-end generator, but the backend part will be ours. Just something to consider.

from generator-ng-fullstack.

@jgodi, good to hear! =]

Also, noted about the server, should not be hard to separate things, but we'll have to sort the gulp tasks first, so client tasks won't mix with server tasks and suchs. I'm stuck with go integration for now, but I'm keeping an eye on it.

from generator-ng-fullstack.

How about to have a dedicated gitter for this generator?

from generator-ng-fullstack.

@remicastaing, there you go 😄

from generator-ng-fullstack.

Wouldn't be good to have a repository with a generated app to discuss about
the result and about the generator?
Le jeu. 16 avr. 2015 à 12:12, Eric Mendes Dantas [email protected]
a écrit :

@remicastaing https://github.com/remicastaing, there you go
https://gitter.im/ericmdantas/generator-ng-fullstack [image: 😄]

—
Reply to this email directly or view it on GitHub
#14 (comment)
.

from generator-ng-fullstack.

We can use the gh-pages branch for that possibly.

from generator-ng-fullstack.

I would love to get @kingcody's feedback on this as he is quite active on generator-angular-fullstack and may bring some interesting ideas to this in addition to expertise.

from generator-ng-fullstack.

Closing this. Better discuss in separate issues.

from generator-ng-fullstack.