react-apollo v2.2.3 Release Notes
Release Date: 2018-09-30 // over 5 years ago-
๐ Bug Fixes
- Mutation errors are now properly returned as a render prop, when using
a default
errorPolicy
ofall
. @amacleay in #2374 <Mutation />
refetchQueries
triggered by name (string) will now use the correct variables. @fracmal in #2422
๐ Improvements
- Replace the
lodash
dependency withlodash.flowright
(since that's the only non-devlodash
function we're dependent on). Devlodash
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 falsyelement
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
toMutationOptions
. @danilobuerger in #2354 - ๐ Typings: more
MutationOptions
changes/fixes. @danilobuerger in #2340 - โ Remove
allowSyntheticDefaultImports
use. Typescript'sallowSyntheticDefaultImports
compiler option is something we'd like to start using, but we jumped the gun a bit by introducing it in https://github.com/apollographql/react-apollo/commit/9a96519d390783dfd9a431dc2dbaa476a24f7b80. Including it means that anyone who wants to use Typescript with React Apollo would have to also include it in their own localtsconfig.json
, to be able to handle default imports properly. This is because we're also using Typescript'ses2015
module
option, which meansallowSyntheticDefaultImports
has to be enabled explicitly. We've switched back to using a combination ofimport * as X
andrequire
syntax, to work with default imports. We'll re-introduceallowSyntheticDefaultImports
use in React Apollo 3. @hwillson in #2438
- Mutation errors are now properly returned as a render prop, when using
a default