Release v14.0.0
Problem
Let's coordinate on releasing this final version, @IvanGoncharov and @mjmahone. I believe #1382 is the final blocker based on previous discussions I've had with you all about what we'd like to include. If there's anything else we should have blocking this release let me know. Next steps are to write up the full release notes with special mentions of breaking changes, then finally push the version bump and commit tag.
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: Release v14.0.0
@leebyron There is a couple issue I think we need to discuss: 1. After #1373 merged we still have a few related issues: 1. `validateSchema` doesn't use nodes from new `extensionASTNodes` properties. 2. `extend scalar` is not supported 1. I also think it's very critical to add validation of directives in SDL since as noted here no one validates them correctly at the moment. That will lead t
Trust Score
1 verification
- 1
@leebyron There is a couple issue I think we need to discuss:
1. After #1373 merged we still have a few related issues: 1. `validateSchema` doesn't use nodes from new `extensionASTNodes` properties. 2. `extend scalar` is not supported 1. I also think it's very critical to add validation of directives in SDL since as noted here no one validates them correctly at the moment. That will lead to a situation very similar to the recent `Allow interfaces to have no implementors`. Since spec defines set of validation rules but no one implements them. Probably we shouldn't enforce `Directives Are Unique Per Location` until https://github.com/facebook/graph
Validation
Resolved in graphql/graphql-js GitHub issue #1383. Community reactions: 0 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep