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
Hey, team. Really appreciate you guys work on this project.
Without it I can't migrate my existing Rails app into a SPA base on nodeJS. Or I need to try to figure out what the hell react-router is going on, which I think is too complete and brilliant to me, my app is a tiny one.
Now I face a situation that I need to access query/search in the route object.
For example, I have an endpoint http://www.example.com/?foo=bar. Owing to the different query foo=bar or baz=quz I have to set different state into my template. Is it possible we have the parsed query as a default params in context object just like params?
Right now I use this library for parsing in client side, and access with req.query in server side. But I think it maybe cool if we pre-parsed it.
I can come with a PR if you buy this one.
thanks
The text was updated successfully, but these errors were encountered:
Hey, team. Really appreciate you guys work on this project.
Without it I can't migrate my existing Rails app into a SPA base on nodeJS. Or I need to try to figure out what the hell react-router is going on, which I think is too complete and brilliant to me, my app is a tiny one.
Now I face a situation that I need to access query/search in the route object.
For example, I have an endpoint
http://www.example.com/?foo=bar
. Owing to the different queryfoo=bar
orbaz=quz
I have to set different state into my template. Is it possible we have the parsed query as a default params in context object just like params?Right now I use this library for parsing in client side, and access with
req.query
in server side. But I think it maybe cool if we pre-parsed it.I can come with a PR if you buy this one.
thanks
The text was updated successfully, but these errors were encountered: