Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

introduce pruneSchema function, PruneSchema transform, and pruneSchema options for makeExecutableSchema and stitchSchemas #1632

Merged
merged 5 commits into from Jun 11, 2020

Conversation

yaacovCR
Copy link
Collaborator

Some of these options won't work, as there is a minimal level of pruning built into v6 healSchema and mapSchemas. This default pruning should probably be removed in v7, as we cannot necessarily make assumptions as to who wants what pruned.

Motivation: #1624

@theguild-bot
Copy link
Collaborator

theguild-bot commented Jun 11, 2020

The latest changes of this PR are available as alpha in npm: 6.0.10-alpha-fa07fd1.0

Quickly update your package.json by running:

npx match-version @graphql-tools 6.0.10-alpha-fa07fd1.0

consider removing minimal level of pruning built into healSchema and mapSchema in the next major version, as built in pruning makes it impossible to build unpruned schemas, which may be of use to some library users
@yaacovCR yaacovCR merged commit fa07fd1 into master Jun 11, 2020
@yaacovCR yaacovCR deleted the prune-unused-types branch June 11, 2020 13:40
@ardatan ardatan added the feature New addition or enhancement to existing solutions label Jun 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New addition or enhancement to existing solutions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants