chore(deps): update dependency @types/graphql to v14 #27
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 PR contains the following updates:
0.11.7->14.2.3Release Notes
graphql/graphql-js
v14.2.1Compare Source
14.2.1 (2019-03-31)
Bug Fix 🐞
v14.2.014.2.0 (2019-03-26)
Note: Updating to this release can cause new Flow errors since it adds Flow typing for
printfunction that was missing in previous versions.New Feature 🚀
Bug Fix 🐞
Docs 📝
Polish 💅
42 PRs were merged
Internal 🏠
17 PRs were merged
Committers: 7
v14.0.2Compare Source
Fixes:
ValidationRuleflow type is now exported (#1505)v14.0.1Compare Source
(Something went wrong during release, this version has been unpublished)
v14.0.0Thanks to all contributors for the hard work put into this release, which complies with the latest June 2018 version of the GraphQL Spec
Breaking:
VariablesDefaultValueAllowedvalidation rule, andProvidedNonNullArgumentsbecameProvidedRequiredArguments(#1274)onOperation,onFragment, andonField(#1385, #1429)GraphQL*Configare now exact types (#1391, #1443)BreakingChangeTypeandDangerousChangeTypefor detecting adding args and input fields changed name (#1492)formatErrorAPI changed for error message extensions. To upgrade without changing existing server responses, wrapgraphql'sformatError:New:
extendSchemaextended with spec-compliant SDL extensions (#1373, #1392, #1441)symbol.toStringTagsupport (#1297)getOperationRootType(schema, operationAST)(#1345)validateSchemaworks with Schema extensions (#1410)validateworks on SDL definitions (#1438, #1383)experimentalVariableDefinitionDirectivesflag (#1437, #1454)isDefinitionNodeandisTypeSystemDefinitionNode(#1459)isRequiredArgumentandisRequiredInputFieldpredicates (#1463)Fixed:
introspectionFromSchemahas default options (#1408)buildSchemamemory leaks and infinite recursion fixed (#1417, #1427)watchcommand fixed (#1449)validation(#1471)Deprecated:
These will be removed in v15
introspectionQuery, usegetIntrospectionQuery(#1386)getDescription, use the schema AST node to get descriptions (#1396)isValidJSValue, usecoerceValue(#1386)isValidLiteralValue, use validation (#1386)v0.13.2Compare Source
New:
Fixes:
v0.13.1Compare Source
New:
.mjsfiles for module code to support native esmodules (#1244)extendSchema(#1222)isValidNameErrorutility is now exported as a non-throwing alternative toassertValidName(#1237)ExectuableDefinitionNodeFlow type is now exported (#1241)Fixes:
extendSchemanow preserves (and allows extending) a list of legacy field names which would otherwise be considered invalid (#1235)7e68984)v0.13.0Breaking:
'graphql/language/kinds'no longer directly exports enum values #1221New:
getDescriptionhelper function is now exported (#1165)parse(text, {allowLegacySDLEmptyFields: true})(#1171)introspectionFromSchemautility function (#1187)lexicographicSortSchemautility function (#1208) (#1220){allowedLegacyNames: ['__badName']}(#1194)Fixed:
allowedLegacyNameswhen usingextendSchema(#1226) (added since v0.13.0-rc.1)v0.12.3Compare Source
Fixes:
v0.12.2Compare Source
Fixes:
v0.12.1Compare Source
Flow Type Fixes:
experimental.const_paramsFlow option to ensure support for projects which do not enable this option (#1157, #1160)visit()to returnanyinstead ofmixedto reduce the scope of the breaking change of adding Flow types for this function.v0.12.0🎁 Happy Holidays, GraphQL.js v0.12.0 is brings some of the biggest new changes of the year 🎉
This release includes new spec-compliance to existing experimental features, dramatically improves the quality of flow types, and introduces a number of new features and improved behaviors. As a result, there are a number of breaking changes to be aware of, especially for those building tools with GraphQL.js. A huge thank you to everyone who contributes to and uses GraphQL.js.
For a complete list of everything new, see the comparison to the last release.
New and Potentially Breaking:
Schema is now validated as part of a new exported function
validateSchema()instead of during construction. (#1124)This exciting change allows the creating GraphQLSchema instances which are not yet valid, for example: representing types which don't yet have fields. This is very useful for those building schema directly from the new schema definition language. The new function
validateSchema(), much like the existingvalidate(), will return an Array of GraphQLError describing all issues with a schema. This also now includes blame sites in the original schema definition language, allowing much more helpful error messages when a schema is invalid. This might be breaking if your codebase relied on GraphQLSchema or any of the GraphQL type definition classesValidation errors for value literals (and variable values) are greatly improved, doing so results in a change to the standard set of validation rules. (#1126, #1133, #1144, #1153)
Code which relied on repeating the standard validation rules, or filtered them down using whitelists or blacklists may need to be updated. The rules
ArgumentsOfCorrectTypeRuleandDefaultValuesOfCorrectTypeRulehave been removed and are replaced with two new rulesValuesOfCorrectTypeRuleandVariablesDefaultValueAllowedRule. While the quality of validation errors are improved by this change, this does not actually cause any existing valid documents to become invalid or vice-versa.GraphQL can now execute synchronously if all resolvers are synchronous functions. This means
execute()may no longer return a Promise if execution completed synchronously. Thegraphql()function will still always return a Promise, but a newgraphqlSync()function guarantees synchronous completion (or throws if any resolver does not complete). This unlocks exciting new use cases for querying over static data-sets and caches. (#1115, #1120)Update to match Schema definition language latest specification. (#1102, #1117, #1139)
The schema definition language has some slight changes from the original experimental version through the standardization process. New
extendforms were added and previously valid forms which omit fields liketype Foo {}are now syntax errors and can be replaced withtype Footo indicate that fields are not yet defined.Descriptions in the schema definition language are now represented as preceding strings rather than comments. (#927)
This change follows the latest updates to the spec proposal (https://github.com/facebook/graphql/pull/90) after a long discussion between the merits of comments vs. literals as descriptions. To ease the migration to this latest change, existing comment-descriptions can still be used by providing options to the relevant functions. To read a SDL that uses comments as descriptions,
buildASTSchema(document, { commentDescriptions: true }); to write an SDL using comments as descriptions,printSchema(schema, { commentDescriptions: true }).Allow serializing scalars as null. (#1104)
Since
nullis a potentially valid value for a scalar to serialize to in some rare conditions, this change ensures that scalars which serialize tonullno longer produce errors. This is breaking since custom scalars which relied on returningnullto indicate failure should now either returnundefinedor throw an Error.Flow types for the parsed GraphQL AST and GraphQL Errors are now read only. This may result in new flow errors being detected in your codebase if you manipulate ASTs and Errors. (#1116, #1121, #1122)
New & Improved:
visit(). As with any flow type improvement, this could expose real issues with your existing codebase. (#1155)instanceoffor any use of GraphQL.js (#1137)GraphQLNonNullandGraphQLListare now flow typed as covariant and operate like a function instead of a class. This means that you should no longer typenew GraphQLList(someType)and instead favorGraphQLList(someType). (#1136)printError()is exported which highlights any blame lines from the original sources. Useful for printing errors to consoles. (#1129, #1131)getIntrospectionQuery()is exported, and the existingintrospectionQueryconstant is deprecated. This helps improve the flow types and allows for some flexibility and options. (#1113)isSpecifiedScalarType,isIntrospectionType, andisSpecifiedDirective(#924).findBreakingChanges()andfindDangerousChanges()Fixed:
visit()for leaving visitors. (#1149)73b804b)GraphQLArgsflow type is now exported. (#1118)isDeprecatedinstead ofdeprecationReasoninprintDeprecated()(#1035)buildASTSchema(),extendSchema()andbuildClientSchema(). (#903)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.