-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix bug related to readonly properties #87
Conversation
According to this comment, let me take another look at the code. |
Based on laravel/framework#51877 (comment) I'll close this for now but definitely appreciate the help here 👍 Just want to prevent this from getting merged unwanted. Feel free to continue the discussion and send in a new PR if you figure things out. Thanks! |
@driesvints Never mind. Based on laravel/framework#51877 (comment), the fix is feasible. Should I go ahead and resubmit the same PR? |
@rust17 re-opened this one for ya 👍 |
Alright, just give me some time. |
Thank you for the background information and the test case included in this PR. This test case shows that removing the fix code reproduces the bug caused by the readonly property, while adding the code resolves it. |
This pull request fix this issue where an exception is thrown during the unserialize process when
Bus::chain
handles a class that includes a readonly property. The exception message is:Cannot modify readonly property Illuminate\Tests\Integration\Queue\ReadonlyEnumTestJob::$enum
.