[PropertyAccess][VarExporter] isReadable fails on lazy objects’ non-existent properties
#54068
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MatTheCat
changed the title
isReadable fails on lazy objects’ non-existent propertiesisReadable fails on lazy objects’ non-existent properties
|
Will be fixed by #54194 👌 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In the LexikJWTAuthenticationBundle, there is a call to
PropertyAccessor::isReadableto access the correct user identifier (see lexik/LexikJWTAuthenticationBundle#1037). The issue is: if the user instance is a lazy object (because it is an entity fetched from a relation e.g.), this call will fail instead of returningfalse.Following #51919 (comment), this PR only contains a failing test case for now.