[1.x] Make inertia response more extension friendly #632
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 simply aims to make
Inertia\Response
more friendly to extension/customization by:toResponse
methodThis unlocks, for example, customizing how the
page.url
get's resolved by Inertia.In a particular case, it was necessary for me to ensure redirections keept the url fragment (
/abc#123
).Previously I had to:
Example implementation
Now, a custom Response class overwritting the
resolveUrl
method could be resolved from the container whenever an Inertia response is returned.Example implementation