[PropertyAccess] [For reference only] Allow custom property accessors #38515
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.
Disclaimer: this is just a relaunch of PR #22190 targeting "5.x" instead of "master". @fabpot asked to create this PR because he's not able to switch the target repository as the old PR is already closed. Take into account that this code was intended to be merged into 3.4 a loooong time ago...
Here is the first of the two PR related to #18016. This implements changes on the
PropertyAccess
component and will be followed by another one leveraging the new features into theFrameworkBundle
.Now it is possible to override the property accessors (getters, setters, adders and removers) using annotations or YAML config files. Metadata is automatically cached in the pool configured for the property path cache.
Some examples of how to use the new feature:
Annotations:
YAML:
XML: