fix(core): add hash symbol in uri parse, closes #1943

[olegshilov]

What kind of change does this PR introduce? (check at least one)
Described here: #1943

• Bugfix
• Feature
• New Binding Issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change? (check one)

• Yes. Issue #___
• No

The PR fulfills these requirements:

• When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

[amrbashir]

Since this PR is touching the #, I am a little concerned about hashed routes, will this affect how they behave or not (sry, can't test it atm)?

Ideally two things should be working:

1. Routing within a SPA by calling the hashed router respective methods, for example: vue-router's router.go(1) or router.push('route-name').

2. Navigating to a hashed route like tauri://custom-protocol/#/nested/route as if you type it in the address bar of a normal browser. maybe @lucasfernog can have more insight on how we might test this in tauri context

[lucasfernog]

Since this PR is touching the #, I am a little concerned about hashed routes, will this affect how they behave or not (sry, can't test it atm)?

Ideally two things should be working:

1. Routing within a SPA by calling the hashed router respective methods, for example: vue-router's router.go(1) or router.push('route-name').
2. Navigating to a hashed route like tauri://custom-protocol/#/nested/route as if you type it in the address bar of a normal browser. maybe @lucasfernog can have more insight on how we might test this in tauri context

Hash route does not trigger the custom protocol, it is handled by the router framework. Since the hash portion is just an anchor, it doesn't trigger a new page load.

[lucasfernog]

I'll test this anyway.

[lucasfernog]

Works like a charm, tested with a Vue router hash mode app (https://github.com/mayank091193/quasar-scrum) and it didn't affect it since the hash URLs doesn't even hit the custom protocol.

[amrbashir]

My bad then, I thought directly navigating to a hashed route would still try to go through custom protocol.

Thanks for the PR @olegshilov