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 Jul 15, 2019. It is now read-only.
I guess the way I'm trying to do this is not the fluxible way, so could you point me in the right direction.
Should I use the navParams to pass the query string values to the route and therefore define optional query string parameters in the path of the route (as asked in the issue #42)?
Getting back to the issue, I think I have omitted an important point in my previous message:
I would like to avoid as much as possible the utilization of href and more generally any type of hard coded URL. This should prevent me from having to go through the entire application's source-code and check if / how to update URLs when a change occurs in the pattern of one URL.
Hi Guys,
First of all, awesome job here, this really helped me kick start my React project.
I have an issue though, I would like to be able to pass query string parameters to:
I guess the way I'm trying to do this is not the fluxible way, so could you point me in the right direction.
Should I use the navParams to pass the query string values to the route and therefore define optional query string parameters in the
path
of the route (as asked in the issue #42)?Thanks,
Ben
The text was updated successfully, but these errors were encountered: