backport parser typescript type-definitions for 15.x.x release #3251
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
saihaj
approved these changes
Aug 27, 2021
IvanGoncharov
added
the
PR: bug fix 🐞
|
@n1ru4l Thanks 👍 |
|
@IvanGoncharov Any updates or ETA on the release of 15.5.2? |
|
@n1ru4l Released |
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.
The 15.x.x release line did not have type definitions for the
Parserclass. We added type-definitions within our code-base, but with version 16.x.x being released that causes issues. Thus the easiest solution would be to have both type-definitions being provided from graphql-js.