[3.x] Preserve URL fragment across redirects with server-side preserveFragment option#2897
Merged
Conversation
retainFragment optionpreserveFragment option
preserveFragment optionpreserveFragment option
This file contains hidden or 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
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 adds support for the
preserveFragmentpage property on the client side. When the server includespreserveFragment: truein the Inertia page object, the URL fragment from the original request is preserved on the final URL, even across redirects.Currently, URL fragments are only retained when the request URL and response URL match. This means fragments are lost during redirects (e.g.,
POST /formredirecting to/result), even though the client knows the intended fragment.The server-side implementation is in inertiajs/inertia-laravel#829, where you may chain
preserveFragment()on a redirect response: