makeExtendSchemaPlugin: add ability to define field scope as part of plans #1920
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.
Description
Can now define field scope as part of plans:
This still averts the need for
embed()
used in V4.Further, have made the system automatically guess the scope for connection types, so when using a connection type all the arguments you'd expect (first, last, before, after, offset, condition, orderBy, etc) are automatically added. You can disable this by overwriting the scope as shown above, but setting
undefined
as the values for the keys.Fixes graphile/crystal-pre-merge#476
Performance impact
Build-time only.
Security impact
None known.
Checklist
yarn lint:fix
passes.yarn test
passes.RELEASE_NOTES.md
file (if one exists).If this is a breaking change I've explained why.