Set propertyResolved after evaluating the AbstractCallableMethod#708
Merged
Conversation
jasmith-hs
force-pushed
the
property-resolved
branch
from
f123078 to
03a0f0f
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is more in line with the other delegates for resolving properties. Currently, when this is called first, if there are any unresolved properties within the method, (since the ELContext is shared), then we'll think that the method could not be resolved, even if it was. By setting
propertyResolvedtotrueafter the operation takes place, we ensure that the boolean value represents whether the current method was resolved, rather than some nested property being resolved.