-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Migration to Angular 1.3 #639
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
Comments
ngMessage can be used to now show the validation errors on forms (login, signup) |
I agree, 1.3 has lots of improvements that I personally have been tracking for a while now. Anyone else here reviewed it against their builds yet? I haven't noticed many breaking changes that would affect the project but I certainly haven't tested extensively. |
currently i'm using ALL packages for npm at their latest version available and fullstack works perfectly. My plan was next to upgrade angular to 1.3 and see in how far it immediately works |
👍 Agreed, definitely want to upgrade this asap. |
+1 |
There should be an AngularJS version option (like all the others). |
that makes it very very difficult at least in some places i believe. imho a fork would be more appropiate and easier to maintain |
I had a related issue (#693). Is the generator for AngularJS 1.2 only? If so, why does it pull in 1.3 components? |
The IE8 support drop is not a big deal as it does not mean that it will be broken, just that it won't be officially supported. |
@Toub I think that would be the best option. |
Angular 1.3 has just been released.
Would be nice to migrate!
https://docs.angularjs.org/guide/migration#migrating-from-1-2-to-1-3
The text was updated successfully, but these errors were encountered: