sibelius / relay-workshop

Material for my Relay Workshop
https://react-europe-relay-workshop.now.sh/
169 stars 11 forks source link

build(deps): bump relay-compiler from 15.0.0 to 16.0.0 #2827

Closed dependabot[bot] closed 11 months ago

dependabot[bot] commented 11 months ago

Bumps relay-compiler from 15.0.0 to 16.0.0.

Release notes

Sourced from relay-compiler's releases.

v16.0.0

Breaking

  • Arguments passed to the filters keyword for the @connection directive will now throw if they are invalid instead of being a no-op. [2dd79543d3f6]

Flow-related breaking changes:

  • Explicit type annotations are no longer needed for commitMutation [603ce546741a] and useMutation [051e4694c20b].
  • Records can no longer be modified directly and can only be passed to utility functions such as those in RelayModernRecord.js. [21a896c54e63]
  • Added the babel-plugin-syntax-hermes-parser plugin, which switches Babel to use hermes-parser instead of @babel/parser, and enables full syntax support for Flow. [c320a892482c]
  • [1d95ce251653] - Make React.Element fully opaque

TypeScript-related breaking changes:

  • Empty variables will now be typed as Record<PropertyKey, never> instead of as {} to represent an object without properties. [16910c948e9a] (#4404)
  • Nullable fields will now yield a union of the actual type, null and undefined (T | null | undefined) instead of (T | null). To keep the old type generation behavior for now, you may set the typescriptExcludeUndefinedFromNullableUnion feature flag in the relay-compiler config as follows. Note the feature flag will be removed in a future release. [cc47bc95414b] (#4380)
    • Update: We will leave the feature flag available indefinitely, or until we have an explicit solution to missing data. See this issue for more context.
{
  "language": "typescript",
  "typescriptExcludeUndefinedFromNullableUnion": true
}

Bug Fixes

  • [313d62d2e96f] - Don't assign to frozen objects and arrays
  • [a5e0ba35d72f] - Fix flow errors in the reactive executor and relay runtimes
  • [17f4abf1eb59] - Make isWithinUnmatchedTypeRefinement be set on a per-fragment basis
  • [33d5475eba9b] - Fix RelayObservable ifEmpty: Cannot access 'current' before initialization
  • [41233831f88c] - Do not freeze array buffer views
  • [a2c2b6453702] - Get compiler playground working again (#4336)
  • [04005db54643] - Replace invalid variable characters for import name (#4293)
  • [0fce632a4882] - Fix refetching and pagination when using a custom nodeInterfaceIdField (#4053)
  • [e784ee42756b] - Fix version number parsing in cannotReadPropertyOfUndefined__DEPRECATED (#4314)
  • [a79038b77b3d] - Fix some grammar in validation selection conflict error messages
  • [6f30869b2896] - Updating connection handler to be able to deal with streamed edges that are already in memory
  • [2699206e9757] - Always use / as path separators in generated artifacts (to allow stable compilation between windows and unix-based systems)

Experimental

Relay Resolvers are an experimental feature of Relay which allows you to model derived data, and soon client state, in your Relay graph. Since our last release we’ve put considerable work into stabilizing the feature. This includes bug fixes across our compiler, type generation, runtime and LSP (editor integration). In particular, contributors have fixed a number of bugs which made it impossible to use Relay Resolvers with TypeScript.

Documentation:

  • [bd95f00a1010] - Updates RelayResolvers docs to include terse syntax and updates to the module resolution details

Improvements:

  • [15c2715fc203] - Fix compiler issue with stale artifacts for Resolvers in watch mode (#4415)
  • [0b2791feeebe] - skip_redundant_nodes: do not mess with order of selections within inline fragments with client edge metadata
  • [77304c284152] - Add flag and validation for strict resolver flavors
  • [3d66ad8907e1] - Add artifact with schema resolvers
  • [998fd498a104] - Regression test for not detecting undefined variables on resolver fields
  • [556d696fe4e8] - Fix Relay Resolver typegen for Typescript-based projects (#4274)
  • [508dca3b96ce] - Add handleMissedUpdates to subscription callback

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 11 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.