query params go before the hash about bide

[heyarne]

I would disagree; this is actually very useful behavior as it allows me to pass arguments in a more flexible way; the reload behavior can be controlled by me and I don't have to know all params a route will take in advance. You can still use the "real" query parameters, no?

[jiangts]

so I'm using the router to define both html5 history routes on the client side, as well as to define API endpoints I want to hit on the server.

When the query params are in the wrong place, my server's query parser can't find the params so I can't send params in my GET requests.