fix(hash): second time redirect page no effect #927
Closed
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
|
Thank you but I'm not sure about this. The correct way would be to restore the history like in #921. Did you find a case where that fix was failing? |
Hi @posva . I think I find a solution about this. |
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.
This PR is about #916.
I think we should not throw
NAVIGATION_DUPLICATEDifredirectedFromexists, and at the same timefrom,targetLocation&redirectedFromare not the same value.I tested this PR with the case in #916 and it works. Feel free to let me know if I need to add the corresponding tests. :-)
Fix #916