| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| 2.5.3.tar.gz | 2019-03-25 | 263.1 kB | |
| 2.5.3.zip | 2019-03-25 | 341.9 kB | |
| README.md | 2019-03-25 | 3.2 kB | |
| Totals: 3 Items | 608.2 kB | 0 | |
2.5.3
Bug Fixes
- Fixed an infinite loop caused by using
setStatein theonError/onCompletedcallbacks of theQuerycomponent.
@chenesan in #2751 - Fixed an issue that prevented good results from showing up in a
Querycomponent, after an error was received, variables were adjusted, and then the good data was fetched.
@MerzDaniel in #2718 - Fixed an issue that prevented
Querycomponent updates from firing (under certain circumstances) due to the internallastResultvalue (that's used to help prevent unnecessary re-renders) not being updated.
@Glennrs in #2840
Improvements
MockedProvidernow accepts achildPropsprop that can be used to pass props down to a child component.
@miachenmtl in #2482onCompletedcallbacks now use a destructuring-friendly type definition.
@jozanza in #2496@connectiondirectives are now properly stripped fromMockedResponse's, when usingMockedProvider.
@ajmath in #2523MockedProviderhas been updated to stop setting a defaultresolversvalue of{}, which means by default Apollo Client 2.5 local resolver functionality is not enabled when mocking withMockedProvider. This allows@clientfields 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