This repository has been archived by the owner on Nov 23, 2020. It is now read-only.
chore(deps): update apollo graphql packages #527
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:
1.2.1
->1.3.5
1.5.1
->1.6.6
2.5.1
->2.6.10
1.2.11
->1.2.14
2.10.1
->2.11.0
2.5.4
->2.5.8
Release Notes
apollographql/apollo-client
v1.3.5
Compare Source
v1.3.4
Compare Source
v1.3.2
Compare Source
isEqual
without pulling in massivelodash.isequal
.@benjamn in #4924
v1.3.1
Compare Source
isEqual
function has been reimplemented using thelodash.isequal
npm package, to better support circular references. Since thelodash.isequal
package is already used byreact-apollo
, this change is likely to decrease total bundle size.@capaj in #4915
v1.3.0
Compare Source
apollographql/apollo-link
v1.2.14
Compare Source
v1.2.13
Compare Source
v1.2.12
Compare Source
Avoid importing
graphql/language/printer
forgetKey
.@benjamn in #992
Documentation updates.
@jsjoeio in #1044
Bump
apollo-utilities
to reduce total bundle size.@salzhrani in #1044
apollographql/graphql-tag
v2.11.0
Compare Source
package.json
sideEffects
changes to clearly identify thatgraphql-tag
doesn't have side effects.@hwillson in #313
v2.10.4
Compare Source
graphql
15.@adriencohen in #299
v2.10.3
Compare Source
index.d.ts
declaration file.@Guillaumez in #289
v2.10.2
Compare Source
index.d.ts
declaration file.@hwillson in #285
apollographql/react-apollo
v2.5.8
Compare Source
2.5.8 (2019-06-21)
Bug Fixes
apollo-client
2.6.3'sObservableQuery.resetQueryStoreErrors
method optional, for people who can't update to
react-apollo
's newapollo-client
peer dep of 2.6.3.@hwillson in #3151
v2.5.7
Compare Source
Improvements
MockedProvider
is using the proper CJS/ESM bundle, whenreferencing
ApolloProvider
.@jure in #3029.
ApolloContext
definition to play a bit more nicely withReact.createContext
types.@JoviDeCroock in #3018
when using the
graphql
HOC.@andycarrell in #3008
MockLink
to improvedebugging experience used by
MockedProvider
.@evans in #3078
Bug Fixes
apollo-client@beta
peer dep.@brentertz in #3064
null
, when using thegraphql
HOC.@ZhengYuTay in #3056
query
being mandatory in thefetchMore
signature.@HsuTing in #3065
Query
component to get stuck in an alwaysloading state, caused by receiving an error (meaning subsequent valid
responses couldn't be handled). The
Query
component can now handle anerror in a response, then continue to handle a valid response afterwards.
@hwillson in #3107
Subscription
component code to avoid setting state on unmountedcomponent.
@jasonpaulos in #3139
loading
state fornetwork-only
fetch policy.@jasonpaulos in #3126
v2.5.6
Compare Source
Improvements
Both the
Query
component andgraphql
HOC now accept areturnPartialData
prop. This is an important new feature, that shouldhelp address a lot of open Apollo Client / React Apollo issues, so we'll
explain it here with an example. Before this release, if you run a query
that looks like:
in one component, the results are cached, then you run a superset query like
the following in another component:
Apollo Client will not re-use the partial data that was cached from the first
query, when it preps and displays the second component. It can't find a
cache hit for the full second query, so it fires the full query over the
network.
With this release, if you set a
returnPartialData
prop totrue
on thesecond component, the
data
available to that component will beautomatically pre-loaded with the parts of the query that can be found in the
cache, before the full query is fired over the network. This means you can
do things like showing partial data in your components, while the rest of the
data is being loaded over the network.
v2.5.5
Compare Source
Improvements
ApolloContext
).@MrLoh in #2961
Renovate configuration
📅 Schedule: "after 11pm,before 6am" in timezone Europe/Warsaw.
🚦 Automerge: Disabled due to failing status checks.
♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by WhiteSource Renovate. View repository job log here.