Add livewire hook to refresh page on 419 error. #105
Merged
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
Livewire provides a way to define a callback, that gets called if a 419 error occurred. For our dashboard, we most likely want to refresh the page if this happens, so that our updates run again.
dbohn
changed the title
dbohn
changed the title
|
Thanks! |
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.
Thank you for this awesome package!
The documentation says, that the livewire routes should be excluded from the CSRF verification to enable permanent refreshing.
This seems a bit odd to me, especially if there are other pages, that use livewire, in the same app.
On the other hand, livewire provides a way to define a callback, that gets called if a 419 error occurred, instead of the default confirm dialog.
As we most likely want to refresh our dashboard in this case to preserve refresh capabilities, the page could be refreshed without any confirmation.
Maybe I'm not seeing the complete picture here, but I thought this might be a suitable change for a dashboard!