fix: @defer
directive is duplicated when schema already has one
#235
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 a quick-fix for users on the router with a schema that supports defer.
The defer code merged into
main
manually adds the@defer
directive to the schema because it is still an experimental spec directive. This is causing a duplicate directive error and is blocking codegen.All the Swift codegen tests for defer as being skipped now. This is OK-ish because defer is disabled in the JS frontend anyways so nobody can actually generate deferred operation models from
main
. This will be reverted in thefeature/defer-execution-networking
branch.