Docs: Enhance moveCard() examples with database transaction support#87
Open
AtemD wants to merge 1 commit intorelaticle:4.xfrom
Open
Docs: Enhance moveCard() examples with database transaction support#87AtemD wants to merge 1 commit intorelaticle:4.xfrom
AtemD wants to merge 1 commit intorelaticle:4.xfrom
Conversation
Added examples for custom card movement logic with transaction handling to ensure data integrity.
AtemD
changed the title
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
1 participant
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.
Summary
Added examples for custom card movement logic with transaction handling to ensure data integrity.
PR Description:
What does this PR do?
Updates the
Integration Patternsdocumentation to include a recommendedDB::transactionwrapper when overriding themoveCard()method.Why is this necessary?
The current documentation shows custom logic executing after
parent::moveCard()has already committed to the database. If a developer implements multi-table logic (like creating an activity log or triggering a complex state machine) and that logic throws an exception, the database becomes out of sync (the card moved, but the dependent logic failed).Wrapping the method in a transaction ensures true atomicity. If the developer's custom logic fails, the card movement rolls back safely, and Livewire should gracefully returns the card to its original column on the frontend. This makes Flowforge much safer for enterprise or for such specific use cases!