Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: Allow reacting to search params and fragment changes on the client side #509

Open
agj opened this issue Jan 7, 2025 · 0 comments

Comments

@agj
Copy link

agj commented Jan 7, 2025

Some way to react within the route itself to changes in the URL involving search params (?) and the fragment (#). Something like Elm Land's Page.withOnUrlChanged, although I haven't used that personally.

My personal use case is that I have a static blog built with elm-pages, and one page is the tag page, which uses a ?t=tag query to list posts matching a tag. I was able to do this with v2 because when the URL changed, the page re-initted, so the model was rebuilt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant