Fix issue with path in query plan's deferred nodes #2281
Merged
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.
The
path
currently included in the query plan for deferred nodes is a "response" path, meaning that it's essentially a path in a json object. But for deferred node, the idea was that the path, alongside thesubselection
that the deferred node also include, could be used to rebuild the subset of the query corresponding to the deferred part it represents, but becausepath
misses fragments, this is not always possible to do.This patch changes the
path
format to include fragments so it can be used to rebuild queries more directly (the new format also do not include@
for lists: this gets in the way of rebuilding queries from the path more than it helps, and ever when using thepath
to walk on responses, it's easy enough to handle lists without needing this).