validation: Add missing rule exports #2399
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
IvanGoncharov
added
the
PR: feature 🚀
IvanGoncharov
added a commit
to IvanGoncharov/graphql-js
that referenced
this pull request
Jan 26, 2020
Backport of graphql#2399 on `14.x.x` branch
IvanGoncharov
added a commit
that referenced
this pull request
Jan 26, 2020
Backport of #2399 on `14.x.x` branch
IvanGoncharov
added a commit
to IvanGoncharov/graphql-js
that referenced
this pull request
Jan 27, 2020
Technically it's not a breaking change since only stuff exported from `graphql` and `graphql/validation` are part of public API. However, many tools/libraries depended on this "internal" imports to blacklist certain rules so in graphql#2399 I added missing exports so now you can import them like so: ``` import { ExecutableDefinitionsRule } from 'graphql/validation'; ``` Also I backported missing exports to `14.6.0` release. If this change broke your code please try to migrate it as shown above and please feel free to open an issue if you need assistance with migration.
IvanGoncharov
added a commit
to IvanGoncharov/graphql-js
that referenced
this pull request
Jan 27, 2020
Long awaited change, see this disscussion: graphql#808 (comment) Technically it's not a breaking change since only stuff exported from `graphql` and `graphql/validation` are part of public API. However, many tools/libraries depended on this "internal" imports to blacklist certain rules so in graphql#2399 I added missing exports so now you can import them like so: ``` import { ExecutableDefinitionsRule } from 'graphql/validation'; ``` Also I backported missing exports to `14.6.0` release. If this change broke your code please try to migrate it as shown above and please feel free to open an issue if you need assistance with migration.
IvanGoncharov
added a commit
that referenced
this pull request
Jan 27, 2020
Long awaited change, see this disscussion: #808 (comment) Technically it's not a breaking change since only stuff exported from `graphql` and `graphql/validation` are part of public API. However, many tools/libraries depended on this "internal" imports to blacklist certain rules so in #2399 I added missing exports so now you can import them like so: ``` import { ExecutableDefinitionsRule } from 'graphql/validation'; ``` Also I backported missing exports to `14.6.0` release. If this change broke your code please try to migrate it as shown above and please feel free to open an issue if you need assistance with migration.
This was referenced Feb 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.