Fix doubling hash in React StrictMode #1728
Open
+4
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TomKalina
changed the title
jrson83
added a commit
to inertiajs-revamped/inertia
that referenced
this pull request
Apr 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
We are having the following problem in our application.
We are using
<React.StrictMode>in the application, this causes the application to redirect twice in dev mode.This forces us to double the previous hash during development because it calls the same router logic twice.
For example it makes
exanple.com/#hibecomeexanple.com/#hi#hiafter the updateThis fix would prevent that from happening. If so, would you have handled this differently?
Thank you very much for Inertia! It's a cool project 😉