Skip to content
This repository has been archived by the owner on May 29, 2019. It is now read-only.

https://www.polymer-project.org/1.0/blog/routing #1769

Closed
gertcuykens opened this issue Oct 1, 2016 · 4 comments
Closed

https://www.polymer-project.org/1.0/blog/routing #1769

gertcuykens opened this issue Oct 1, 2016 · 4 comments

Comments

@gertcuykens
Copy link

gertcuykens commented Oct 1, 2016

image

needs to be return {path: '/store/garden', prefix: '', __queryParams: {}}

else queryParams doesn't work becasue it isn't active https://jsbin.com/meriqix/edit?html,output

I have no idea if this is actually more like a bug?

@arthurevans
Copy link

@rictic Neither queryParams nor __queryParams works for me, at least in this jsbin. Is this jsbin weirdness, or is there a bug here (in docs or router)? Certainly, it doesn't seem like the user should ever be setting a value with two underscores in front of it.

@rictic
Copy link
Contributor

rictic commented Oct 3, 2016

We renamed queryParams to __queryParams on route objects to discourage people from accessing them directly, and instead using the queryParams property on app-route. __queryParams is correct here, if you're generating a route object yourself then you're a power user.

Logging q in the jsbin works when observing it directly: https://jsbin.com/siximavede/edit?html,output

@arthurevans
Copy link

Thanks @rictic!

@gertcuykens
Copy link
Author

Ok thanks, closing it 👍

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

No branches or pull requests

3 participants