This repository has been archived by the owner on Jul 21, 2019. It is now read-only.
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.1.23
->0.4.3
2.10.0
->2.10.1
2.3.3
->2.5.8
Release Notes
apollographql/apollo-client
v0.4.3
Compare Source
v0.4.2
Compare Source
v0.4.1
Compare Source
v0.4.0
Compare Source
v0.3.1
Compare Source
v0.3.0
Compare Source
v0.1.28
Compare Source
v0.1.27
Compare Source
v0.1.26
Compare Source
v0.1.25
Compare Source
v0.1.24
Compare Source
apollostack/graphql-tag
v2.10.1
Compare Source
Set
by rocwang in #190apollographql/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
v2.5.4
Compare Source
Bug Fixes
Could not find "client" in the context of ApolloConsumer
errors whenusing
MockedProvider
.@hwillson in #2907
Query
components using afetchPolicy
ofno-cache
have theirdata preserved when the components tree is re-rendered.
@hwillson in #2914
Improvements
@afenton90 in #2932
v2.5.3
Compare Source
Bug Fixes
setState
in theonError
/onCompleted
callbacks of theQuery
component.@chenesan in #2751
Query
component, after an error was received, variables were adjusted, and then
the good data was fetched.
@MerzDaniel in #2718
Query
component updates from firing (undercertain circumstances) due to the internal
lastResult
value (that's usedto help prevent unnecessary re-renders) not being updated.
@Glennrs in #2840
Improvements
MockedProvider
now accepts achildProps
prop that can be used to passprops down to a child component.
@miachenmtl in #2482
onCompleted
callbacks now use a destructuring-friendly type definition.@jozanza in #2496
@connection
directives are now properly stripped fromMockedResponse
's,when using
MockedProvider
.@ajmath in #2523
MockedProvider
has been updated to stop setting a defaultresolvers
value of
{}
, which means by default Apollo Client 2.5 local resolverfunctionality is not enabled when mocking with
MockedProvider
. This allows@client
fields to be passed through the mocked link chain, like peoplewere used to before AC 2.5. When using this default mode you will see a
dev only warning message about this like:
This message can be safely ignored. If you want to use
MockedProvider
with AC 2.5's new local resolver functionality, you can pass your local
resolver map into the
MockedProvider
resolvers
prop.@ajmath in #2524
Improvements to the
graphql
HOC generics forfetchMore
andrefetch
.@EricMcRay in #2525
The
ApolloProvider
/ApolloConsumer
implementations have been refactoredto use React 16.3's new context API.
@wzrdzl in #2540
All
dependencies
anddevDependencies
have been updated to their latestversions, and related Typescript changes have been applied.
@hwillson in #2873
v2.5.2
Compare Source
Bug Fixes
Context
type fromtypes.ts
instead ofwalkTree.ts
,to reenable
import { Context } from 'react-apollo'
(which has beenbroken since 2.4.0).
@benjamn in #2825
Improvements
Add
examples/rollup
to enable application-level bundle measurement and demonstrate Rollup configuration best practices.
@benjamn in #2839
Bundle size reductions inspired by
examples/rollup
app.@benjamn in #2842
v2.5.1
Compare Source
Bug Fixes
MockedProvider
enables Apollo Client 2.5's local state handling,and allow custom / mocked resolvers to be passed in as props, and used with
the created test
ApolloClient
instance.@hwillson in #2825
v2.5.0
Compare Source
Improvements
features, as well as many overall code improvements to help reduce the React
Apollo bundle size.
#2758
MockedResponse
result
when usingMockedProvider
, such that every time the mocked result is returned,the function is run to calculate the result. This opens up new testing
possibilities, like being able to verify if a mocked result was actually
requested and received by a test.
@hwillson in #2788
v2.4.1
Compare Source
Improvements
Adds a
onSubscriptionComplete
prop to theSubscription
component, thatcan be passed a callback to be called when the subscription observable
is completed.
@sujeetsr in #2716
During server-side rendering,
ObservableQuery
objects created inprevious rendering passes will now be preserved in later passes (within
the same
getDataFromTree
orgetMarkupFromTree
call), so that errorscan be handled properly when using the
errorPolicy: "all"
option.PR #2753
v2.4.0
Compare Source
Bug Fixes
onCompleted
/onError
even ifMutation
unmounts.PR #2710
Improvements
walkTree
function has been deprecated, since there's no way tomake its behavior consistent with the latest versions of React. To save
bundle size,
walkTree
is no longer exported fromreact-apollo
,though you can still access it as follows:
Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "
rebase!
".👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot. View repository job log here.