You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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
witharg1
beingnull
would lead to/myPlace//arg2Value
). It then should be decoded asnull
for the follow updidNavigate
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 theotherwise
route takes place. We thus need to work around this, until we possibly replace it with our own lighter version.The text was updated successfully, but these errors were encountered: