Skip to content

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

Closed
Toub opened this issue Oct 14, 2014 · 11 comments
Closed

Migration to Angular 1.3 #639

Toub opened this issue Oct 14, 2014 · 11 comments

Comments

@Toub
Copy link

Toub commented Oct 14, 2014

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

@eikaramba
Copy link

ngMessage can be used to now show the validation errors on forms (login, signup)

@kingcody
Copy link
Member

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.

@eikaramba
Copy link

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

@DaftMonk
Copy link
Member

👍 Agreed, definitely want to upgrade this asap.

@zbitname
Copy link

+1

@dcunited08
Copy link

There should be an AngularJS version option (like all the others).

@eikaramba
Copy link

that makes it very very difficult at least in some places i believe. imho a fork would be more appropiate and easier to maintain

@ErikEvenson
Copy link

I had a related issue (#693). Is the generator for AngularJS 1.2 only? If so, why does it pull in 1.3 components?

@Toub
Copy link
Author

Toub commented Nov 11, 2014

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.
Instead of restrict generator-angular-fullstack to angular 1.2 (and create a fork for 1.3 and later) I would create a IE8 branch (to allow people to fork it) and go further to angular 1.3 now!

@kingcody
Copy link
Member

@Toub I think that would be the best option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants