Skip to content
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.

AngularJS 1.2.x doesn't support routes with empty parameters #65

Closed
alex3683 opened this issue Sep 8, 2014 · 1 comment
Closed

AngularJS 1.2.x doesn't support routes with empty parameters #65

alex3683 opened this issue Sep 8, 2014 · 1 comment

Comments

@alex3683
Copy link
Member

alex3683 commented Sep 8, 2014

If a parameter in a navigateRequest is null or empty, it is encoded as the empty string in the place url (e.g. something like /myPlace/:arg1/:arg2 with arg1 being null would lead to /myPlace//arg2Value). It then should be decoded as null for the follow up didNavigate event.
With AngularJS this isn't possible anymore due to changed regular expressions in ngRoute (angular/angular.js#1745). The route simply isn't matched and a redirect to the otherwise route takes place. We thus need to work around this, until we possibly replace it with our own lighter version.

@alex3683
Copy link
Member Author

alex3683 commented Sep 8, 2014

Fixed in master (v0.14.0) and release-0.13.x (v0.13.2).

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

No branches or pull requests

1 participant