fix: securityPostDenormalize not working because clone is made after denormalization #5182
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.
Support for
security_post_denormalize
was added in #4184.At that moment, the clone to populate previousObject was made before denormalization. It worked well.
This commit moved the clone after denormalization.
After upgrading to 3.0, using
security_post_denormalize
on a anApiProperty
was not working anymore. Moving the$previousObject
line to its first position fixed the issue on my project.I believe this issue will be fixed too.