Fix case when SerializableClosure uses as class property #86
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
Dry7
force-pushed
the
fix/serializable-closure-class-property
branch
from
1d33df7 to
c5f82d0
Compare
Dry7
force-pushed
the
fix/serializable-closure-class-property
branch
from
c5f82d0 to
274f5c7
Compare
|
I've recently run into this problem as well when mixing Batches and Jobs inside a chain() |
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 pull request fix the case when SerializableClosure is used as one of the class properties.
At the moment, it is SerializableClosure replaced by a Closure.
This behavior was the cause of this issue laravel/framework#51897