Eddie Monge Jr

the optional comment actually makes it more complicated. that makes it even harder to automate. As for it the the user is using bower install, i would think that works...

you could always rename them yourself and update the references. Having them be mixed case caused more problems. lower cased file names are better for web stuffs anyway since most...

Reopening this and will add behavior so the file name follows the angular:xyz name. Lets see how many bugs that generates :8ball:

The issue is that this is a scaffold generator. When you say `yo angular:something someName`, you aren't specifying a filename; you are specifying the name for that component. Since this...

The bug for this in the current implementation is at #526

The source of the many bugs was the bug that the filename didn't get the same treatment. Thats been fixed in the latest release. Long term, choosing what casing you...

this really isnt an upgrade blocking issue. nothing new yet. still slowly working on adding these things in

The fonts from bootstrap shouldnt be in `styles/fonts`. They should be in `bower_components/bootstrap/dist/fonts`

Again, the bootstrap fonts should not be copied to `styles/fonts` so the vendor.css reference should not change. Any font files you manually put in `app/styles/fonts` should get copied over and...

Try updating to 0.12.1 and see if that fixes it