Conversation
Member
|
Honestly the code should probably just bail if the batch record has been deleted? |
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 fixes a
TypeErrorthat can occur when a batchthen()callback deletes the batch and afinally()callback is also registered.Batch::invokeCallbacks()previously assumed$this->fresh()always returned aBatchinstance. If thethen()callback deleted the persisted batch row, the laterfinally()callback receivednull, violatinginvokeHandlerCallback()'s non-nullableBatchparameter.This now falls back to the current in-memory batch instance when
fresh()returnsnull.