Add attribute support, remove deprecations, unify JMSParser
#51
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.
Preferred
annotation1.x
JMSParser(Test)
When
readonly
became a reserved word in PHP 8.1, it was required to have two implementations of theJMSParser
. One for versions below PHP 8.0, and one for PHP 8.1 and higher.However, the jms serializer library itself renamed the offending class to
DeprecatedReadOnly
(with an alias to the old class name) and it also extends theReadOnlyProperty
attribute, so having a separate class for it in here is no longer necessary.Fixes #46 and #48
@dbu While this would theoretically be everything required for a
2.0
release, I just wanted to mention that I'm also working on adding support for discriminators, though this could also be added with2.1
.