fix(deps): update apollo graphql packages #147

renovate · 2018-10-05T13:58:57Z

This PR contains the following updates:

Package	Type	Update	Change	References
graphql-tag	dependencies	minor	`2.8.0` -> `2.10.0`	source
react-apollo	dependencies	minor	`2.0.4` -> `2.2.4`	source

Release Notes

apollostack/graphql-tag

Fix IE11 support by using a regular for-loop by vitorbal in #176

`v2.9.0`

Compare Source

Remove duplicate exports in named exports by wacii in #170
Add experimentalFragmentVariables compatibility by lucasconstantino in #167

apollographql/react-apollo

`v2.2.4`

Compare Source

Bug Fixes

lodash.isequal was improperly set as a dev dependency for
MockLink / MockedProvider. It is now a dependency.

@danilobuerger in #2449

Improvements

The Subscription component now accepts a fetchPolicy prop.

@MatthieuLemoine in #2298

Typescript

Make sure the TVariables generic is passed to ObservableQuery.

@tgriesser in #2311

`v2.2.3`

Compare Source

Bug Fixes

Mutation errors are now properly returned as a render prop, when using
a default errorPolicy of all.

@amacleay in #2374
<Mutation /> refetchQueries triggered by name (string) will now use the correct variables.

@fracmal in #2422

Improvements

Replace the lodash dependency with lodash.flowright (since that's the
only non-dev lodash function we're dependent on). Dev lodash
dependencies have also been updated to use their individual module
equivalent.

@hwillson in #2435
Removed rollup-plugin-babel-minify as it's no longer being used.

@hwillson in #2436
Small getDataFromTree.ts logic adjustment to avoid unnecessary calls
when a falsy element is encountered.

@HOUCe in #2429
graphql 14 updates.

@hwillson in #2437
All example apps (included in the repo) have been updated to work with the
latest version of React Apollo.

@hwillson in #2439

Typescript

Fix lodash typings.

@williamboman in #2430
Typings: added context to MutationOptions.

@danilobuerger in #2354
Typings: more MutationOptions changes/fixes.

@danilobuerger in #2340
Remove allowSyntheticDefaultImports use. Typescript's
allowSyntheticDefaultImports compiler option is something we'd like to
start using, but we jumped the gun a bit by introducing it in
9a96519.
Including it means that anyone who wants to use Typescript with React
Apollo would have to also include it in their own local tsconfig.json, to
be able to handle default imports properly. This is because we're also using
Typescript's es2015 module option, which means
allowSyntheticDefaultImports has to be enabled explicitly. We've
switched back to using a combination of import * as X and require
syntax, to work with default imports. We'll re-introduce
allowSyntheticDefaultImports use in React Apollo 3.

@hwillson in #2438

`v2.2.2`

Compare Source

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

`v2.2.1`

Compare Source

Revert: "Typescript: use Partial<TData> instead of TData | {}, for the
QueryResult data property."

`v2.2.0`

Improved TypeScript Typings:
Deprecated MutationFunc in favor of MutationFn.
Added missing onCompleted and onError callbacks to MutationOpts.

@danilobuerger in #2322
Added an example app that shows how to test mutations.

@excitement-engineer in #1998
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
Allow a custom cache object to be passed into the test-utils
MockedProvider.

@palmfjord in #2254
Make the MockedProvider mocks prop read only.

@amacleay in #2284
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
Avoid importing lodash directly.

@shahyar in #2045
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
No longer building against Node 9

@hwillson in #2404
Make sure <Subscription />, <Query /> & <Mutation /> all support
using an Apollo Client instance configured in the context or via
props.

@quentin- in #1956
Typescript: use Partial<TData> instead of TData | {}, for the
QueryResult data property.

@tgriesser in #2313
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
Fixed a regression where variables passed in graphql HOC options were
not merged with mutation variables.

@samginn in #2216
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

`v2.1.11`

Fixed an issue in getDataFromTree where queries that threw more than one
error had error messages swallowed, and returned an invalid error object
with circular references. Multiple errors are now preserved.

@anand-sundaram-zocdoc in #2133
Update both the <Mutation /> component and graphql HOC to accept a new
awaitRefetchQueries prop (boolean). When set to true, queries specified
in refetchQueries will be completed before the mutation itself is
completed. awaitRefetchQueries is false by default, which means
refetchQueries are usually completed after the mutation has resolved.
Relates to Apollo Client.

PR #3169.

@hwillson in #2214
Typings adjustment: pass TData along into MutationUpdaterFn when using
MutationOpts, to ensure that the updater function is properly typed.

@danilobuerger in #2227
Check if queryManager is set before accessing it.

@danilobuerger in #2165

`v2.1.9`

Added onCompleted and onError props to the Query component, than can
be used to register callback functions that are to be executed after a
query successfully completes, or an error occurs.
@jeshep in #1922
Add UNSAFE_componentWillMount SSR support.
@leops in #2152
Clear out scheduler on MockedProvider unmount.
@danilobuerger in #2151

`v2.1.8`

Addressed deployment issue.

`v2.1.7`

The ApolloProvider children prop type has been changed from element
to node, to allow multiple children.
@quentin- in #1955
Properly support the new getDerivedStateFromProps lifecycle method.
@amannn in #2076
lodash is no longer pinned to version 4.17.10.
@cherewaty in #1951
README updates to replace apollo-client-preset with apollo-boost.
@JamesTheHacker in #1925
README updates to fix broken links.
@DennisKo in #1935
Project README has been updated to show a <Query /> example.
@petetnt in #2102

`v2.1.6`

Adjust getDataFromTree to properly traverse React 16.3's context API
provider/consumer approach.
@marnusw in #1978
An ApolloClient instance can now be passed into a Mutation
component via a prop named client. This prop will override
an ApolloClient instance set via context, by the ApolloProvider
component.
@amneacsu in #1890
The ApolloClient instance used by a Mutation is now available in that
Mutation's result.
PR #1945
@cooperka in #1945

`v2.1.5`

Dependency updates to align with typescript changes made in
apollo-client 2.3.3
PR #2105

`v2.1.4`

Adds __typename for queries made with MockProvider and MockLink

`v2.1.3`

Fixed issue where refetch was not possible after SSR
Fixed overly resubscribing from Subscription and allow passing function to determine shouldResubscribe

`v2.1.2`

Simplified the MockedProvider API #1882
Fixed test-utils export

`v2.1.1`

Fixed an issue in getDataFromTree where queries that threw more than one
error had error messages swallowed, and returned an invalid error object
with circular references. Multiple errors are now preserved.

@anand-sundaram-zocdoc in #2133
Update both the <Mutation /> component and graphql HOC to accept a new
awaitRefetchQueries prop (boolean). When set to true, queries specified
in refetchQueries will be completed before the mutation itself is
completed. awaitRefetchQueries is false by default, which means
refetchQueries are usually completed after the mutation has resolved.
Relates to Apollo Client.

PR #3169.

@hwillson in #2214
Typings adjustment: pass TData along into MutationUpdaterFn when using
MutationOpts, to ensure that the updater function is properly typed.

@danilobuerger in #2227
Check if queryManager is set before accessing it.

@danilobuerger in #2165

`v2.1.0`

Officially release new components!

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.

fix(deps): update apollo graphql packages

5b4f6a5

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update apollo graphql packages #147

fix(deps): update apollo graphql packages #147

renovate bot commented Oct 5, 2018

fix(deps): update apollo graphql packages #147

Are you sure you want to change the base?

fix(deps): update apollo graphql packages #147

Conversation

renovate bot commented Oct 5, 2018

Release Notes

Bug Fixes

Improvements

Typescript

Bug Fixes

Improvements

Typescript

Renovate configuration