-
Notifications
You must be signed in to change notification settings - Fork 482
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
Optional route params with pre-rendered views #275
Comments
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 |
Thanks for your fast reply. I'll close the other issue on angular/router. |
@alexpods will take this issue |
@zanettin @gdi2290 The bug is in core router library. More precisely it's here. As you can see @zanettin Could you open the issue in core angular2 repository? UPDATE |
thanks for your time @alexpods! i've re-opened the issue on the core router repo. |
@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). |
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 |
Thank you... my bad. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
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?
issue assigned to: @alexpods
The text was updated successfully, but these errors were encountered: