Preserve field ordering by adding placeholder values for deferred fields #2
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.
During execution if a field returns a future the value doesn't get
assigned to the results dictionary until after that future is resolved.
So if there is a mix of deferred and non-deferred fields in a query the
non-deferred fields will always get returned first regardless of the
request ordering.
This PR fixes this issue by adding a placeholder to the result object
that gets overridden when the future gets resolved. That way field
ordering is preserved.
Fixes #1
Diff-Id: 94549