Handling hash router behavior #14
Description
I noticed when you use the hash router with this client that the ticket gets appended in the middle of the URL. The URL starts off as
https://localhost/test/#/search
After a successful authentication, It looks like this which doesn't resolve,
https://localhost/test/&ticket=ST-353-JPhvHh6qh1ThXdk0cdkN-idirems.com#/search?status=in_process
The build-url library seems to add the query params first and then everything after the hash at the end of the URL which I would expect. I think the status part should be done before the hash. Is this what should be expected?