Some tasks run twice now.

The order is also wrong, things like test and deploy should run last

Things like $resource and model.

they should be hidden from editor searches

Obviously things need to change.

• ngDocs does not work well under the same server as the main application.
• Tests should not be run by gulp, as it takes a lot longer to see the test result after a save
• The default gulp task should not start the server
• The gulp serve task should start the default gulp watchers ? ? ? ( this is where it gets weird )

So what will the user commands be ?

gulp serve
gulp
npm test ( or karma start karma.conf.js )
gulp serve-docs

But then how would the development/production environments factor into this ?

gulp serve-prod
gulp serve-dev ( same as gulp serve )

Then what would the commands that get run at the same time be ?

gulp serve
npm test
gulp serve-docs

Usage only.

No generators for .jade files, just generators to setup the environment to handle jade templates

how to prefix suffix a controller/directive/etc
how to build the file name based on the controller/directive/etc name

how to suffix .js file name with type of object

make everything relative to

/src/app

for a webapp and

/src/module

for a module

Some files use tabs instead of spaces.

This is a mistake and will be fixed really soon.

This project will use spaces not tabs, to stay consistent with 99% of the javaScript projects out there.

This has happened twice in the last month.

Both times, I was running gulp watchers and ran another task independently which modified things and triggered gulp inject watchers in the other gulp process ...

This seems to be a recipe for disaster.

Currently I do this a lot by running gulp ngdocs, since that can't be watched. If you're running gulp ngdocs while running gulp watchers, make sure you have a backup of your index.html

Object names

Directives

Directives will always be expected to be camelCased, and their html representations to be dash-cased

Controllers

Controllers can have flexible names. These settings wouldn't be needed for the webapp-angular:controller generator, as the exact name can be passed in there, however, webapp-angular:route is supposed to be able to automatically build controller names.

Suffix

Suffix your controllers with a string ( examples: Controller, Ctrl )

Prefix

Prefix your controllers with :

• a java style namespace ( examples com.myCompany.ExampleController , some.dots.exampeController )

Capitalization

• java style : capitalize your controller name ( example : ExampleController )
• standard : ( example : exampleController )

Services and Factories

Name can be passed directly when created.

File Names

Naming Conventions

Java Style

MyAngularDirective.js
MyAngularController.js
MyAngularControllerTest.js

Angular-Webapp

my-angular.directive.js
my-angular.directive.spec.js
my-angular.resource.js
my-angular.model.spec.js

Google Best Practice Example

userlogin-directive.js
userlogin-directive_test.js
userlogin-service.js
userlogin-service_test.js

Object to File Name translation

!

running it manually fixes it : gulp ngdocs

but when ran by the gulp watcher spawned by the gulp default task, the ngdocs page is broken

the fix is of course : running it by hand :

gulp ngdocs

Something like

<div ng-include="'some/path/to/file.html'"></div>

If some/path/to/file.html does not exist the page containing this tab, will break badly, and possibly crash your browser.

This is I think, because of the live reload server, being configured to only serve one route /. If the page doesn't exist, the live reload server serves the / route again, which causes an infinite loop since the / route is served to itself / .

If this happens, make sure your includes are ok on that page, for now.

• configuration
• automated generators
• documentation

Generator meant to allow configuring all subgenerators.

Module that can be imported into multiple applications.

karma-inject should run anytime a new bower component is installed

karma would still need to be restarted, unless running under gulp

Currently using gulp-webserver.

This is suggested by gulp-connect as being the recommended web server for gulp.

It is also black listed by gulp as not being a gulp plugin, and they suggest this alternative : https://github.com/gulpjs/gulp/blob/master/docs/recipes/server-with-livereload-and-css-injection.md

m e
h

should probably not keep them inside the plugin

current one actually generates a factory

Error: Unable to read "/usr/local/lib/node_modules/generator-angular-webapp/generators/app/templates/.gitignore" file (Error code: ENOENT).

This error to be fixed in 0.1.4.

The generator cannot be used after installing with npm install. It can only be used with npm link at the moment.

The fix for this will be changing the .gitignore filename to gitignore

Great generator,

I wish I would have started this by forking it. I need to learn some good things from the way it uses gulp.

https://github.com/Swiip/generator-gulp-angular

After reviewing this with a co-worker, got some interesting suggestions :

• the generator should not be opinionated, and allow for very customizable setups, such as allowing to define naming conventions
• the generator should allow defaults to be set, so that less questions are asked when a generator is ran
• the generator should assist as best as possible in producing very loosely coupled modules, that can then be pieced together in another angular-webapp

• ngResource
• angular-local-storage
• angular-translate
• moment.js

paths should be in variables then reused

what i'm seeing is, i have a spec failure, and when running gulp, the serve task never runs because of the error in the specs.

this is a really annoying feature of gulp, exiting on any sort of error, and it's a complete show stopper for any one shop stop gulp task with watchers.

we'll have a work around in angular-webapp, and then wait for gulp to fix their issue in 4.0 as discussed here : gulpjs/gulp#71