-
Notifications
You must be signed in to change notification settings - Fork 71
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
Consider module conventions #11
Comments
Done! :-) |
Whoa? :D The spec isn't even written |
Well, started considering what was decided so far lol :) - I guess we can reopen. I was on a closin' spree! |
I feel ya! :D |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I started a discussion right here: https://gist.github.com/PascalPrecht/5411171#angular-module-structure-proposal
And Brian wrote a blog post about it: http://briantford.com/blog/angular-bower.html
I think fixing #7 depends on these resources, since there'll be possibly a kinda spec which to follow when developing angular modules. :)
The text was updated successfully, but these errors were encountered: