-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[1.11][User] Reduce usage of deprecated \Serializable
interface #13642
#13921
Conversation
@lchrusciel I think we should base this PR on 1.11 branch, what do you think? |
Yes, there is no BC break. I don't see that I'm on the master. It's for 1.11 not for 1.12 |
The base of this pull-request was changed, you need fetch and reset your local branch Unless you added new commits (to this branch) locally that you did not push yet, Feel free to ask for assistance when you get stuck 👍 |
Thanks, Sadetdin! 🎉 |
@lchrusciel my terminal will thanks you for merging my PR :p |
This PR was merged into the 1.11 branch. Discussion ---------- | Q | A | |-----------------|--------------------------------------------------------------| | Branch? | 1.11 | Bug fix? | no | | New feature? | no | | BC breaks? | no | | Deprecations? | no | Related tickets | | | License | MIT | <!-- - Bug fixes must be submitted against the 1.10 or 1.11 branch(the lowest possible) - Features and deprecations must be submitted against the master branch - Make sure that the correct base branch is set To be sure you are not breaking any Backward Compatibilities, check the documentation: https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html --> This is not needed anymore since #13921 Commits ------- 1009082 Remove custom error level on Phpspec
Remove deprecated message of
\Serializable
interface inUser
entity which is reported in PHP 8.1.__serialize
and__unserialize
methods to cover serializationserialize
andunserialize
internal to prevent usage of them (we can remove in next version).