Add support for fragment parameters in the reitit-frontend module

[just-sultanov]

Hi there!

I ran into a problem when developing a SPA-application (without backend) that in the reitit-frontend is no way to process fragment parameters. I use supabase, google and github as oauth providers, which returns response using fragment parameters.

I need to process the fragment parameters due to the fact that the authorization server returns a callback in the following format: https://example.com/#/oauth/google/callback#access_token=foo&refresh_token=bar&provider_token=baz&token_type=bearer&expires_in=3600

This small PR allows us to process fragment parameters the same way we process query parameters.

I created a custom router to implement the required business logic, but I think it will be useful for the community, and that's why I opened this PR.

Links:

• https://www.rfc-editor.org/rfc/rfc6749#section-4.2
• https://www.rfc-editor.org/rfc/rfc6749#section-4.2.2

[ikitommi]

Thanks!! and sorry for taking so long.

[Deraen]

I'm reverting this PR. "Fragment parameters" don't exist in URIs; instead, they are just one use-case-specific way to encode key-value data in the fragment string used by, e.g., OAuth.

It makes sense to support this, but this implementation is too high-level and tied to one specific way to encode data in fragment string.

I'll check if we include the fragment string in the match, if not, first step is to add that to match and at least then it will be easy to decode it in any way.