Fix/invalid error propagation custom scalars (backport for 16.x.x) #3838
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
|
Hi @stenreijers, I'm @github-actions bot happy to help you with this PR 👋 Supported commandsPlease post this commands in separate comments and only one per comment:
|
|
I had to do two commits, because I run locally with a newer version of NPM, so the second commit is to restore the original package-lock.json such that github can do its checks. |
|
Any ETA on this backport @IvanGoncharov ? |
|
@stenreijers Sorry for the delay. |
IvanGoncharov
added
the
PR: bug fix 🐞
|
@IvanGoncharov when can we expect a bump on the 16.x branch for a new npm package? |
|
@stenreijers I will do release on Friday 📦 |
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.
This is the same fix for invalid error propagation on custom scalars, but now backported for 16.x.x
see:
#3837