Jason Trill

This would be great. Not only does it match how you would access an actual JS object (`socialGraph.users[0]`), but libs like [Formik](https://github.com/jaredpalmer/formik) use this notation as well for its paths.

Bootstrap could be considered orthogonal to the generator, but I think it's better to leave it as the default option. The [Bootstrapped version](http://i.imgur.com/pNashvE.png) makes gen-ng look like it's done a...

@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,...

Hmm... I can see where using absolute paths relative to the domain root wouldn't be the best default, such as someone serving an ng app from `http://site.com/path/ng-app/`. But I still...

Yeah, my snippet targeted v0.4.0. Thanks for the updated code!

I've found that this solution has the least impact on the Gruntfile. It changes nothing and adds code in one place and one place only, `connect.livereload.options`: ``` js grunt.initConfig({ //...

My only change to the generated Gruntfile is to add that 9-line middleware function to [`connect.options.livereload`](https://github.com/yeoman/generator-angular/blob/master/templates/common/Gruntfile.js#L77). I use the same variable as in `base`, which is `yeoman.app` so I don't...

Yeah, as long as when the middleware function gets called the value of `options.base` is set to the correct target then everything should be fine.

Okay, this is what I ended up with in the `connect.options` task config. Seems to work. ``` js connect: { options: { // ... // Modrewrite rule, connect.static(path) for each...

I don't think I want it any shorter! As is, this almost feels too "clever".