Skip to content
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

AngularJS 1.3 Support? #1452

Closed
tannerlinsley opened this issue Oct 14, 2014 · 16 comments
Closed

AngularJS 1.3 Support? #1452

tannerlinsley opened this issue Oct 14, 2014 · 16 comments

Comments

@tannerlinsley
Copy link

There seem to be breaking changes for a couple of 1.3 things. Is ui-router 100% compatible with these changes?

@amcdnl
Copy link
Contributor

amcdnl commented Oct 14, 2014

Could you be more specific?

@tannerlinsley
Copy link
Author

Yeah, when upgrading to 1.3, I get loads of $animate errors. When looking at the breaking changes introduced in 1.3, there are some parameter and default parameter changes. It specifically says to search your code for the old $animate syntax and replace with the new one. When searching through my bower_components, ui-router comes up once or twice.

https://docs.angularjs.org/guide/migration has more details on it, but I was just wondering if this needed to be addressed.

@AimeeKnight
Copy link

@amcdnl We're also having problems related to issue #1397. Appears the if block to prepend the url with $locationProvider.hashPrefix() is not getting tripped.

@christopherthielen
Copy link
Contributor

#1397 is fixed in master. @tannerlinsley Can I get a plunkr for $animate errors?

@christopherthielen
Copy link
Contributor

Hmm, we already updated the animation code for 1.3.0. See #1364 #1345 #1367

I switched the sample app over to angular 1.3.0 and other than #1397, 0.2.11 seemed to do fine with 1.3.0.

@AimeeKnight
Copy link

@christopherthielen we are having the issue in 0.2.11 as well as 0.2.12 (master). We're using Bower/Require, and it looks like release/angular-ui-router has not been updated with the fix.

@gaarf
Copy link

gaarf commented Oct 15, 2014

👍 am also hoping for quick release of 0.2.12 to bower

@christopherthielen
Copy link
Contributor

I don't know what the error is. I'll need a plunkr in order to determine the bug and fix it.
@AimeeKnight

@christopherthielen
Copy link
Contributor

@christopherthielen we are having the issue in 0.2.11 as well as 0.2.12 (master). We're using Bower, and it looks like release/angular-ui-router has not been updated with the fix.

Are you saying you tried to use bower to grab master? It doesn't work that way, you have to build master yourself. Check the header of angular-ui-router.js and it will probably say 0.2.11. @AimeeKnight please confirm.

@AimeeKnight
Copy link

@christopherthielen Apologies. You're correct.

@musketyr
Copy link

👍 for quick release

@janosgy
Copy link

janosgy commented Oct 15, 2014

+1

@jasonmacdonald
Copy link

Also see issues with how state.href works. It' checks for !$locationProvider.html5Mode(), but in 1.3 the location manager is setting that value to an object, seen below

html5Mode = {
enabled: false,
requireBase: true,
rewriteLinks: true
};

This always evaluates to "true" (despite enabled = false) and therefore all calls to state.href are stripping the "#" from generated urls.

Should I create a separate bug for this?

@klategan
Copy link

+1 for the change to html5Mode() return type. My Urls are not getting prepended with '#' anymore.

@christopherthielen
Copy link
Contributor

Use 0.2.12-pre1 if you need angular 1.3 html5mode support.

Fixed in 7fea1e9
https://github.com/angular-ui/ui-router/blob/master/src/urlRouter.js#L383

Dupe #1458
Dupe #1413
Dupe #1408
Dupe #1397

@christopherthielen
Copy link
Contributor

It there are still problems using angular 1.3, please open a new issue with explicit details, thanks

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

No branches or pull requests

9 participants