-
Notifications
You must be signed in to change notification settings - Fork 249
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
URL params not working on root #122
Comments
Hey, that's interesting. In theory should work. Here're some questions to clarify the situation:
|
I navigate in my browser to /members, it loads. I can see the routing firing. We use navigo to check the route and make an AJAX call to feed data to a datatable on the page. I then manually add /members?something=here to the URL to test it. I add it, hit return. Route doesn't fire. I refresh, still doesn't fire. Param or not, both routes load the same members/index page... |
I tested my URL in extractGETParameters of navigo - it returns the expected result. |
Sorry. One last thing, what's your browser? |
I've only tested in Chrome so far.
…On Tue, 2 May 2017 at 18:40, Krasimir Tsonev ***@***.***> wrote:
Sorry. One last thing, what's your browser?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#122 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABKck-yZeTNo-OLnrsKzIP1UpKMSMUdQks5r12p6gaJpZM4NOQ9P>
.
|
@stoem can you please try the latest 4.7.1 version. That was a bug and should be fixed now. |
Thanks, this works now. |
i follows documentation but i don't how can i get params from url? @krasimir |
@itsgracian this is the section that you are searching for https://github.com/krasimir/navigo#parameterized-urls |
@krasimir thank you |
I'm new to navigo so please excuse if this is a false alarm.
I'm trying to pick up and process URL parameters. My code is as follows:
var router = new Navigo(null, false); router.on({ '/members': function (params, query) { console.log("/members route triggered"); } }) .resolve();
This works fine when I navigate to /members in the browser but fails to fire as soon as I add any kind of GET parameter and load it via the browser.
If I go to the console and test via router.resolve("/members?b=s") then the route fires and query params are available.
The text was updated successfully, but these errors were encountered: