8.7.1 Using a hash is ignored when not using a hash based routing

I do not use the hash based routing, but it looks like the path gets ignored when creating a match.

Here is an example to illustrate, in my app I navigate to the path:

/appointments?#start=2021-01-01&appointmentId=1

However the match on the uses has the following structure:

{
    data: null,
    params: null,
    queryString: "",
    route: { ... },
    url: "appointments"
}

There is no information in the match at all about the hash url, when before this was available in the query option that used to be available. Is there any way to get the hash information? It would be ideal if we didn’t read the url in the browser ourselves because I think it may not be consistently there (especially because we are using a separate router for legacy paths).

Would it make sense to get the hash part included in the match?

Cheers, Felix

[ajorkowski]

Awesome, this looks like it will work really well. I will try to use the new 8.8 version and let you know how it goes. Probably won’t get to it until next week however.

[ajorkowski]

@krasimir Yes I can confirm works great, I was able to upgrade navigo with these changes 😃 I’ll close it now.