Bump relay-runtime from 5.0.0 to 7.0.0

[dependabot-preview]

Bumps relay-runtime from 5.0.0 to 7.0.0.

Release notes

Sourced from relay-runtime's releases.

v7.0.0

7.0.0

Commits: facebook/relay@v6.0.0...v7.0.0

Breaking

• Variables are no longer set in Relay Context when using a QueryRenderer. This means that any product code that was relying on reading variables from RelayContext will break. If you need to access the variables that were set at a query root, the recommended approach is to manually pass them down through the component tree in product code.

• The constructor signature of Store constructor changed; specifically the second argument to the constructor is now an options object. Any product code directly constructing a Store and passing a second argument will need to be updated.

• Relay Compiler no longer relies on graphql-js for query validation. Most of the validation rules we used previous are now part of the RelayParser itself, while the remainder and implemented as transforms (facebook/relay@15e8d22). Additionally, we've removed the concept of RelayIRValidations (facebook/relay@da01bf3), which ran after IR transformation.

• @defer is no longer allowed on inline fragments, since we can’t communicate a loading state with Suspense when used on an inline fragment. @defer is now only supported on fragment spreads.

Added

• RelayCompiler: added a new directive (facebook/relay@3dd79e8) @DEPRECATED__relay_ignore_unused_variables_error to suppress errors that were surfaced after we've migrated from GraphQL NoUnusedVariablesRule to RelayIRTransform validation. GraphQL NoUnusedVariablesRule was not aware of the difference between root (operation) variables and local fragment variables (defined by @​argumentDefinitions) - because of that, it was considering the local fragment variables that have the same name as the root variable as used and did not report the violation. But in Relay compiler, we know this distinction, and we already keep track of the root variables and can report those invalid cases. Unfortunately, this revealed multiple violations that weren't possible to fix without product team involvement. For this purpose, we added a directive that can be used to temporarily suppress the error while teams fix their queries.

Improved

• Relaxed the constraint for @refetchable directive on a fragment: we no longer enforce that the argument for the node field is called id; it can be called anything as long as it’s an ID type.
• Developers can now select the __id field anywhere that __typename can be selected, in order to fetch the internal cache key of an entity. The primary use-case for this is updating records that don’t have an id. Before, updating or deleting such entities would require writing an updater function that traversed from the nearest strong entity (w an id); now, developers can directly target records with e.g. store.get(record.__id) in an updater function.

Fixed

• RelayCompiler: Usage of $variables in Complex objects (or as List Items) is now disabled by RelayParser: facebook/relay@6946e85 This was already unsupported, but Relay previously threw an error later in compilation.
• MockPayloadGenerator: allow null as default value of enum: facebook/relay@6946e85
• Fix display names for containers.
• Fixed @refetchable connection metadata for custom handlers.
• Fixed missing field handler behavior for plural linked fields.
• Fixed getRefetchMetadata to handle both commonjs and esmodules. (#2875)
• Fixed printing require module dependency in generated artifacts. (#2861)

Misc

• Upgraded React peer dependency to 16.9.0.
• Upgraded babel-preset-fbjs to 3.3.0
• RelayCompiler: We've changed the field type and typeCondition in GraphQL IR types to use Relay internal representation of GraphQL type (facebook/relay@2606f32). Before this change, we were directly using graphql-js type instances. But eventually, our goal in Relay compiler is to get rid of the dependency on the graphql-js schema representation and use a faster/less memory intensive representation of the schema. We also build a Schema wrapper: facebook/relay@9e6d919 - that should help us during this migration.

Experimental

• Several performance improvements to the internal implementation of useFragment were shipped.
• Fixed issue to stop tracking mutations as in flight in the RelayOperationTracker when applying the optimistic update; this caused issues with suspending unexpectedly.
• Fixed issue to stop tracking GraphQL subscriptions as indefinitely in flight in the RelayOperationTracker; instead, subscriptions should only be tracked as in flight when they’re waiting for incremental or module payloads. This caused issues with suspending indefinitely in some cases.
• Fixed issue to correctly dispose of ongoing requests when unmounting a useQuery hook; this might happen when useQuery starts a long-lived request, e.g. to poll for real time data.
• Fixed issue in useQuery to not suspend indefinitely when server response doesn’t return all of the requested data. This might occur for example when making selections on abstract types.
• Fixed re-establishing store subscriptions when using useBlockingPagination.
• Fixed pagination with Relay Hooks when using fragments that contain @argumentDefitions.
• Pagination with Relay Hooks is now allowed even if server returns value for hasNextPage as false.
• Several improvements to new experimental representation of connections.

... (truncated)

Commits

• 40b0c16 v7.0.0
• aee90af Extract RelayRequestParams from the Artifacts
• 24732f6 fix(metadata): fix getRefetchMetadata to handle both commonjs and es … (#2875)
• c375587 finish rollout of sort-documents change
• 62a381d add missing . (#2861)
• f1407e3 React sync for revisions 85d05b3...4eeee35
• 1b8d8fa Adding flow strict-local to as many files as possible
• 1e31267 Cleanup $TEMPORARY$object types - 1/n
• 4f2cfa1 Add local state links to v2+ community resources
• c461e0e Add Mindworking logo to siteConfig; Add blog posts to learning resources(v2+)
• Additional commits viewable in compare view

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 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 badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

• Update frequency
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #2333.