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 was archived by the owner on Nov 22, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 22, 2024. It is now read-only.
Optional route params with pre-rendered views #275
Related to this issue => angular/router#397 I'm not sure if this an issue or a missconfig from my side. Do I need to specify the route on the node side specialy or is it a bug from the router itself?
We created our own version of Location Platform so this could really be our fault with the way we're managing the location. If it works on client then it should work with the server rendered view
@zanettin@gdi2290 The bug is in core router library. More precisely it's here. As you can see urlParams are used only in _stringifyMatrixParams() which is called only if we have auxInstructions (see here). So if we don't have auxilary routes then urlParams will never be used.
@zanettin Could you open the issue in core angular2 repository?
@zanettin I've also opened the issue in the core repository angular/angular#7367. I think the core team will be more active to close the issue there (at least I hope so).
Activity
PatrickJS commentedon Feb 15, 2016
We created our own version of Location Platform so this could really be our fault with the way we're managing the location. If it works on client then it should work with the server rendered view
zanettin commentedon Feb 15, 2016
Thanks for your fast reply. I'll close the other issue on angular/router.
[-]optional route params (Question / Bug?)[/-][+]Optional route params with pre-rendered views[/+]PatrickJS commentedon Feb 26, 2016
@alexpods will take this issue
alexpods commentedon Mar 1, 2016
@zanettin @gdi2290 The bug is in core router library. More precisely it's here. As you can see
urlParamsare used only in_stringifyMatrixParams()which is called only if we haveauxInstructions(see here). So if we don't have auxilary routes thenurlParamswill never be used.@zanettin Could you open the issue in core angular2 repository?
UPDATE
toLinkUrl()is called herezanettin commentedon Mar 1, 2016
thanks for your time @alexpods! i've re-opened the issue on the core router repo.
alexpods commentedon Mar 2, 2016
@zanettin I've also opened the issue in the core repository angular/angular#7367. I think the core team will be more active to close the issue there (at least I hope so).
ganeshkbhat commentedon Mar 2, 2016
Raised similar issue fo query shown as ; instead of ? angular/router#397 >> http://stackoverflow.com/questions/35691663/child-url-query-params-shown-with-instead-of/35698213
alexpods commentedon Mar 2, 2016
@ganeshkbhat It's matrix URI
https://www.w3.org/DesignIssues/MatrixURIs.html
http://stackoverflow.com/questions/2048121/url-matrix-parameters-vs-request-parameters
ganeshkbhat commentedon Mar 2, 2016
Thank you... my bad.
angular-automatic-lock-bot commentedon Sep 4, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.