[Docs] Improve example integration with Laravel Livewire #1255
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
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.
The current draft works fine when integrated into "static" Livewire components, however, it doesn't work in cases where the Livewire component reloads its data, be it due to a component method, lifecycle hook or simply because the flow for the component includes an option to reset its data. Old data will be cached into TipTap and new data will not come.
I re-wrote the example to work in these cases, and also for it to be more aligned to Alpine's example, with the only difference that we'll now use Alpine as a proxy for Livewire<->TipTap communication.
If there are any questions, suggestions or jokes, feel free to let me know 馃槃