[Snyk] Upgrade react-relay from 0.0.0-experimental-8cc94ddc to 0.10.0 #473
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
Snyk has created this PR to upgrade react-relay from 0.0.0-experimental-8cc94ddc to 0.10.0. See this package in npm: https://www.npmjs.com/package/react-relay See this project in Snyk: https://app.snyk.io/org/biancajmarin23/project/c96e1297-6676-452c-b4a0-406779494544?utm_source=github&utm_medium=referral&page=upgrade-pr
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 PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade react-relay from 0.0.0-experimental-8cc94ddc to 0.10.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: react-relay
babel-relay-pluginto usegraphql@0.8.2, which supports the latest revision of the GraphQL specification.RelayGraphQLMutationto public API.rollbackmethod toRelayGraphQLMutation.BabelPluginGraphQL).graphiqlPrinterargument to theRelayNetworkDebugconstructor that can be used to print a link to view the request in GraphiQL.setVariables, specifically when using array/object variables (closes #1357).Relay.disableQueryCachingAPI (closes #754), which may be useful running Relay in a server context.IGNOREas arangeBehavior(closes #1337).RelayQuery.cloneWithRoute(see commit de954992), making logging and analytics that relies on query names more accurate.RelayNetworkDebugnow prints an estimated request size (see commit b94ba409).callsToGraphQL/callsFromGraphQL, fixing issues withnull(closes #1256).injectCacheManageronRelayEnvironment(closes #1320).Relay.QueryConfig(closes #1279).GraphQLRangeget correctly deserialized (closes #1293).errorsattributes and non-200 responses (#1163).client:ID, necessitating the use of a path when a refetchable ID would be preferable in order to produce a correct result (commit 928411df).useFakeDatathat you can use to silence the warning when using aRelayContainerwith fake data.Relay.QLstring. See #896RelayStoreData#toJSON.this.props.relay.pendingVariableswhich can be used to access variables from in-flight queries (to e.g. display a component-specific loading spinner).npm run update-schemainside the Relay repo works again.GraphQLQueryRunner(only relevant to users of the non-public cache manager API).rangeBehaviorsfunction to allow non-string calls.subtractRelayQueryis removed.Subscriptionnodes.RelayNetworkDebugis won't do anything unlessconsole.groupCollapsedis available, because otherwise the output is too noisy to be useful.RelayContainernow uses more descriptive names for stateless functional components, instead ofRelay(props => ReactElement).graphql-js0.6.0. Developers interestedin upgrading to
graphql-js0.6.0 might have to make some changes to theirexisting GraphQL schemas. Read the migration guide for more information:
https://gist.github.com/steveluscher/ffc1dfefbb10ad280c8a4c520a5c201c
the console when
DEVis true, andconsole.groupCollapsedandconsole.groupEndare available.this.props.relayprop passed into components byRelay.Containernowexposes
applyUpdateandcommitUpdatemethods for dispatching mutationsin the context of the current
Relay.Environment.RANGE_DELETEmutations can now remove multiple nodes from a connection,because
deletedIDFieldNamecan now point to a plural field.rangeBehaviorsas a function that receives the connectionarguments and returns one of
GraphQLMutatorConstants.RANGE_OPERATIONS.RelayNetworkDebug#initnow lets you pass in aRelayEnvironmentagainstwhich you would like to debug. This does not yet allow you to debug more than
one environment at a time, but at least you can make the choice of which one.
RelayReadyStatenow contains aneventsarray; a stream of events that canbe accessed from a
RelayReadyStateCallback. You can reduce over this list ofevents to implement any kind of custom rendering logic you like.
this.props.variablesnow reflects the variables after being processed withprepareVariables. The fact that variables were the un-prepared values wasa source of confusion for many.
prepareVariablescould be called twice, breakingcomponents with non-idempotent
prepareVariablesfunctions.setVariables, orproduce one through
prepareVariables, that you have not declared ininitialVariablesupfront.staleprop of areadyStateto change even ifthere was previously an
errorpresent.at column 0.
shouldComponentUpdate: () => booleanfunction. If specified, this functionalways overrides the default implementation (ie. there is no fall-through to
the default).
RelayNetworkDebugnow logs query variables.RelayNetworkDebugis now added as a subscriber instead of replacing anyexisting network layers. It also no longer replaces the global
fetch.Relay.Environment#injectNetworkLayer(and, by extensionRelay#injectNetworkLayer) will now warn if injecting would overwrite apreviously injected layer.
RelayGraphQLMutationAPI (still beingfinalized and not yet documented, so use at your own risk).
The following APIs are early versions and are as of yet undocumented so please
use them with caution.
Relay.Environment.Relay.Storeis now simply a global instance ofRelayEnvironment. To create your own isolated store and network subsystem,create a
new RelayEnvironment()and make use of it whereverenvironmentis required.
Relay.Environment#injectNetworkLayerto inject a custom network layerfor use within the context of a particular
Relay.Environmentinstance.Relay.ReadyStateRenderer. This component takes in an instance ofRelay.Environment, aqueryConfigthat conforms to theRelayQueryConfigInterface, and a Relaycontainer. It renderssynchronously based on the supplied
readyState. This primitive enables youto create alternatives to
Relay.Rendererthat fetch and handle data in acustom way (eg. for server rendered applications).
Relay.Renderer– a replacement forRelay.RootContainerthatcomposes a
Relay.ReadyStateRendererand performs data fetching.Relay.RootContaineris now a wrapper aroundRelay.Rendererthatsubstitutes
Relay.Storeforenvironment.RelayRendererRenderCallbacktoRelayRenderCallback.RelayQueryConfigSpectoRelayQueryConfigInterface.RelayContainer.setVariableswill no longer check if the variables arechanged before re-running the variables. To prevent extra work, check the
current variables before calling
setVariables.COMMIT_QUEUEDstate usingRelayMutationTransaction#rollback.NODE_DELETEorRANGE_DELETEmutation config, you canomit
parentIDif your parent, in fact, does not have an ID.Relay will now write
nullinto the store for that field. This allows you toreturn smaller payloads over the wire by simply omitting a key in the JSON
response, rather than to write an explicit
fieldName: null.relayprop does not change between renders, we now recycle the sameobject. This should enable you to make an efficient
this.props.relay === nextProps.relaycomparison inshouldComponentUpdate.arguments (first/last/after/before) so long as the values of those arguments
are variables and not concrete values (eg.
friends(first: $first, last: $last)will no longer cause the Relay Babel plugin to throw).Relay.Mutation.RelayNetworkDebug. Invokerequire('RelayNetworkDebug').init(Relay.DefaultNetworkLayer)to enjoy simpleto read logs of your network requests and responses on the console. Substitute
your own network layer if you use one.
rangeBehaviors:IGNOREmeans the range should not be refetched at all.REFETCHwill refetch the entire connection.information about edges that have already been fetched. This can be enabled by
adding
@ relay(variables: ['variableNames'])to a connection fragment.npm run buildnow works on WindowsurifromRelayQueryConfigSpec. Theuriproperty was part ofRelayRoute, but neverRelayQueryConfig. This revision simply cleans up the Flow shape inRelayContainer.RelayRendererdoes not run queries during synchronous server-side rendering.