Update QueryBuilder to change the type after each transformation #14596
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.
Objective
D
andF
in the QueryBuilder are always up to date so that the query optimizations work but actually this approach doesn't seem to work because:SystemBuilder
often won't have a signature that matches the output of the QueryBuilder.For example I get this error:
However I still think it's worthwhile posting the draft just to demonstrate the approach and to get some feedback
@SkiFire13 @james-j-obrien
Maybe it's actually a feature (and not a bug) to have a Query that iterates on data that doesn't exactly match the types (D, F)?
I know it's already used in
QueryLens
andQueryBuilder
, so maybe it's something we'd like to keep?Maybe a better solution would then be #14348 (comment)