Br fix datarequirements #1256
Merged
Br fix datarequirements #1256
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
… property access #1202: Fixed property access not being reported correctly when it occurred after the initial query context for a retrieve #1202: Fixed data requirements not being reported correctly when a query source was itself a nested query #1202: Fixed duplicate data requirements being reported for property access not directly related to a retrieve #1202: Fixed enableResultTypes not working in some cases
JPercival
approved these changes
Oct 24, 2023
mdnazmulkarim
approved these changes
Oct 24, 2023
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.
This PR fixes several issues related to data requirements analysis, including #1202 and #1203