search

Saeris / mini-movie-db

🎬 Simple clone of The Movie DB built with Preact, Apollo, & Serverless
http://mini-movie-db.netlify.com/
MIT License
7 stars 0 forks source link

An in-range update of react-apollo is breaking the build 🚨 #46

Open greenkeeper[bot] opened 6 years ago

greenkeeper[bot] commented 6 years ago

The dependency react-apollo was updated from 2.1.11 to 2.2.0.

🚨 View failing branch.

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 could not complete due to an error ([Details](https://travis-ci.org/Saeris/mini-movie-db/builds/433599529?utm_source=github_status&utm_medium=notification)).
Release Notes for 2.2.0

2.2.0 (September 26, 2018)

New Functionality

  • The <Subscription /> component now allows the registration of a callback
    function, that will be triggered each time the component receives data. The
    callback options object param consists of the current Apollo Client
    instance in client, and the received subscription data in
    subscriptionData.
    @jedwards1211 in #1966
  • The graphql options object is no longer mutated, when calculating
    variables from props. This now prevents an issue where components created
    with graphql were not having their query variables updated properly, when
    props changed.
    @ksmth in #1968
  • When a query failed on the first result, the query result data was being
    returned as undefined. This behavior has been changed so that data is
    returned as an empty object. This makes checking for data (e.g.
    instead of data && data.user you can just check data.user) and
    destructring (e.g. { data: { user } }) easier. Note: this could
    potentially hurt applications that are relying on a falsey check of data
    to see if any query errors have occurred. A better (and supported) way to
    check for errors is to use the result errors property.
    @TLadd in #1983
  • Avoid importing lodash directly.
    @shahyar in #2045
  • Make sure <Subscription />, <Query /> & <Mutation /> all support
    using an Apollo Client instance configured in the context or via
    props.
    @quentin- in #1956
  • Adjust <Query /> onCompleted and onError callbacks to be triggered
    via the componentDidUpdate lifecycle method. This ensures these callbacks
    can be used when data is fetched over the network, and when data is
    fetched from the local store (previsouly these callbacks were only being
    triggered when data was fetched over the network).
    @olistic in #2190
  • Import lodash/flowRight using ES import to allow for treeshaking.
    @Pajn in #2332
  • Added a new partialRefetch prop (false by default).
    When a Query component is mounted, and a mutation is executed
    that returns the same ID as the mounted Query, but has less
    fields in its result, Apollo Client's QueryManager returns the
    data as an empty Object since a hit can't be found in the cache.
    This can lead to application errors when the UI elements rendered by
    the original Query component are expecting certain data values to
    exist, and they're all of a sudden stripped away. The recommended way to
    handle this is to use the mutations update prop to reconcile the mutation
    result with the data in the cache, getting everything into the expected
    state. This can definitely be a cumbersome process however, so to help
    address this the partialRefetch prop can be used to automatically
    refetch the original query and update the cache.
    @steelbrain in #2003

Bug Fixes

  • When the Query skip prop is set to true, make sure the render prop
    loading param is set to false, since we're not actually loading
    anything.
    @edorivai in #1916
  • Fixed a regression where variables passed in graphql HOC options were
    not merged with mutation variables.
    @samginn in #2216

Testing

Typescript

  • Improved TypeScript Typings:
    Deprecated MutationFunc in favor of MutationFn.
    Added missing onCompleted and onError callbacks to MutationOpts.
    @danilobuerger in #2322
  • Remove duplicate FetchMoreOptions and FetchMoreQueryOptions types, and
    instead import them from Apollo Client.
    @skovy in #2281
  • Type changes for the graphql HOC options.skip property.
    @jameslaneconkling in #2208
  • Typescript: use Partial<TData> instead of TData | {}, for the
    QueryResult data property.
    @tgriesser in #2313

Infrastructure

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:

greenkeeper[bot] commented 6 years ago

After pinning to 2.1.11 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper[bot] commented 6 years ago

Your tests are still failing with this version. Compare changes

greenkeeper[bot] commented 6 years ago

Your tests are still failing with this version. Compare changes

Release Notes for 2.2.2

2.2.2 (September 28, 2018)

  • When using React.createContext and SSR, we now make sure the context
    provider value is reset to the previous value it had after its children are
    walked.
    @mitchellhamilton in #2304
  • Revert:
    When a query failed on the first result, the query result data was being
    returned as undefined. This behavior has been changed so that data is
    returned as an empty object. This makes checking for data (e.g.
    instead of data && data.user you can just check data.user) and
    destructring (e.g. { data: { user } }) easier. Note: this could
    potentially hurt applications that are relying on a falsey check of data
    to see if any query errors have occurred. A better (and supported) way to
    check for errors is to use the result errors property.
    #1983
greenkeeper[bot] commented 6 years ago

Your tests are still failing with this version. Compare changes

greenkeeper[bot] commented 6 years ago

Your tests are still failing with this version. Compare changes

greenkeeper[bot] commented 6 years ago

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

greenkeeper[bot] commented 5 years ago

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

greenkeeper[bot] commented 5 years ago

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

greenkeeper[bot] commented 5 years ago

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

greenkeeper[bot] commented 5 years ago

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

greenkeeper[bot] commented 5 years ago

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

greenkeeper[bot] commented 5 years ago

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 2.5.3

2.5.3

Bug Fixes

  • Fixed an infinite loop caused by using setState in the
    onError / onCompleted callbacks of the Query component.
    @chenesan in #2751
  • Fixed an issue that prevented good results from showing up in a Query
    component, after an error was received, variables were adjusted, and then
    the good data was fetched.
    @MerzDaniel in #2718
  • Fixed an issue that prevented Query component updates from firing (under
    certain circumstances) due to the internal lastResult value (that's used
    to help prevent unnecessary re-renders) not being updated.
    @Glennrs in #2840

Improvements

  • MockedProvider now accepts a childProps prop that can be used to pass
    props 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 from MockedResponse's,
    when using MockedProvider.
    @ajmath in #2523

  • MockedProvider has been updated to stop setting a default resolvers
    value of {}, which means by default Apollo Client 2.5 local resolver
    functionality is not enabled when mocking with MockedProvider. This allows
    @client fields to be passed through the mocked link chain, like people
    were used to before AC 2.5. When using this default mode you will see a
    dev only warning message about this like:

    Found @client directives in query but no client resolvers were specified.
    You can now pass apollo-link-state resolvers to the ApolloClient
    constructor.

    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 for fetchMore and refetch.
    @EricMcRay in #2525

  • The ApolloProvider / ApolloConsumer implementations have been refactored
    to use React 16.3's new context API.
    @wzrdzl in #2540

  • All dependencies and devDependencies have been updated to their latest
    versions, and related Typescript changes have been applied.
    @hwillson in #2873

greenkeeper[bot] commented 5 years ago

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 2.5.4

Bug Fixes

  • Fixes Could not find "client" in the context of ApolloConsumer errors when
    using MockedProvider.
    @hwillson in #2907
  • Ensure Query components using a fetchPolicy of no-cache have their
    data preserved when the components tree is re-rendered.
    @hwillson in #2914

Improvements

greenkeeper[bot] commented 5 years ago

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 2.5.5

Improvements

  • Export the Apollo Context provider (ApolloContext).
    @MrLoh in #2961
greenkeeper[bot] commented 5 years ago

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

greenkeeper[bot] commented 5 years ago

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 2.5.7

2.5.7 (2019-06-21)

Improvements

  • Make sure MockedProvider is using the proper CJS/ESM bundle, when
    referencing ApolloProvider.
    @jure in #3029.
  • Adjust the ApolloContext definition to play a bit more nicely with
    React.createContext types.
    @JoviDeCroock in #3018
  • The result of a mutation is now made available to the wrapped component,
    when using the graphql HOC.
    @andycarrell in #3008
  • Check equality of stringified variables in the MockLink to improve
    debugging experience used by MockedProvider.
    @evans in #3078

Bug Fixes

  • Removed leftover apollo-client@beta peer dep.
    @brentertz in #3064
  • Stop setting optional input to null, when using the graphql HOC.
    @ZhengYuTay in #3056
  • Fix typescript error caused by query being mandatory in the fetchMore
    signature.
    @HsuTing in #3065
  • Fixes an issue that caused the Query component to get stuck in an always
    loading state, caused by receiving an error (meaning subsequent valid
    responses couldn't be handled). The Query component can now handle an
    error in a response, then continue to handle a valid response afterwards.
    @hwillson in #3107
  • Reorder Subscription component code to avoid setting state on unmounted
    component.
    @jasonpaulos in #3139
  • Fix component stuck in loading state for network-only fetch policy.
    @jasonpaulos in #3126
greenkeeper[bot] commented 5 years ago

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 2.5.8

2.5.8 (2019-06-21)

Bug Fixes

  • Makes the use of apollo-client 2.6.3's ObservableQuery.resetQueryStoreErrors
    method optional, for people who can't update to react-apollo's new
    apollo-client peer dep of 2.6.3.
    @hwillson in #3151