Open greenkeeper[bot] opened 6 years ago
After pinning to 2.0.4 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
dependency
react-apollo was updated from 2.1.11
to 2.2.0
.Your tests are still failing with this version. Compare changes
<Subscription />
component now allows the registration of a callbackoptions
object param consists of the current Apollo Clientclient
, and the received subscription data insubscriptionData
.graphql
options
object is no longer mutated, when calculatinggraphql
were not having their query variables updated properly, whendata
was beingundefined
. This behavior has been changed so that data
isdata && data.user
you can just check data.user
) and{ data: { user } }
) easier. Note: this coulddata
errors
property.lodash
directly.<Subscription />
, <Query />
& <Mutation />
all supportcontext
or via<Query />
onCompleted
and onError
callbacks to be triggeredcomponentDidUpdate
lifecycle method. This ensures these callbackslodash/flowRight
using ES import to allow for treeshaking.partialRefetch
prop (false
by default).Query
component is mounted, and a mutation is executedQuery
, but has lessQueryManager
returns theQuery
component are expecting certain data values toupdate
prop to reconcile the mutationpartialRefetch
prop can be used to automaticallyrefetch
the original query and update the cache.Query
skip
prop is set to true
, make sure the render proploading
param is set to false
, since we're not actually loadingvariables
passed in graphql
HOC options
werevariables
.cache
object to be passed into the test-utilsMockedProvider
.MockedProvider
mocks
prop read only.MutationFunc
in favor of MutationFn
.onCompleted
and onError
callbacks to MutationOpts
.FetchMoreOptions
and FetchMoreQueryOptions
types, andgraphql
HOC options.skip
property.Partial<TData>
instead of TData | {}
, for theQueryResult
data
property.dependency
react-apollo was updated from 2.2.0
to 2.2.1
.Your tests are still failing with this version. Compare changes
dependency
react-apollo was updated from 2.2.1
to 2.2.2
.Your tests are still failing with this version. Compare changes
React.createContext
and SSR, we now make sure the contextdata
was beingundefined
. This behavior has been changed so that data
isdata && data.user
you can just check data.user
) and{ data: { user } }
) easier. Note: this coulddata
errors
property.dependency
react-apollo was updated from 2.2.2
to 2.2.3
.Your tests are still failing with this version. Compare changes
dependency
react-apollo was updated from 2.2.3
to 2.2.4
.Your tests are still failing with this version. Compare changes
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 2.1.0 of react-apollo was just published.
This version is covered by your current version range and after updating it in your project the build failed.
react-apollo is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/gursesl/cherrypie/builds/357080794?utm_source=github_status&utm_medium=notification)FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: