Update Apollo GraphQL packages (major) #141
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.9.3->2.4.71.3.2->2.10.0Release Notes
apollographql/apollo-client
v2.4.7Apollo Client (2.4.7)
ApolloClientconstructor has been updated to acceptnameandversionparams, that can be used to support Apollo Server Client Awarenessfunctionality. These client awareness properties are passed into the
defined Apollo Link chain, and are then ultimately sent out as custom
headers with outgoing requests.
@hwillson in #4154
Apollo Boost (0.1.22)
Apollo Cache (1.1.21)
Apollo Cache In-Memory (1.3.11)
Apollo Utilities (1.0.26)
Graphql Anywhere (4.1.23)
v2.4.6Apollo Cache In-Memory (1.3.10)
Added some
returns to prevent errors withnoImplicitReturnsTypeScript rule.
PR #4137
Exclude the
src/directory when publishingapollo-cache-inmemory.Issue #4083
v2.4.5Optimistic tests cleanup.
PR #3834 by
@joshribakoff
Documentation updates.
PR #3840 by
@chentsulin and
PR #3844 by
@lorensr
Implement
ObservableQuery#isDifferentFromLastResultto fixIssue #4054 and
Issue #4031.
PR #4069
Apollo Cache (1.1.20)
readQuerytest to make sure options aren't mutated.@CarloPalinckx in
#3838
Apollo Cache In-Memory (1.3.9)
Issue #4081
PR #4089
Apollo Utilities (1.0.25)
apollo-utilitiesisEqualbug due to missinghasOwnPropertycheck. PR #4072
by @samkline
v2.4.4Apollo Utilities (1.0.24)
Discard property accessor functions in
cloneDeephelper, to fixissue #4034.
Unconditionally remove
cloneDeepproperty accessors.PR #4039
Avoid copying non-enumerable and/or
Symbolkeys incloneDeep.PR #4052
Apollo Cache In-Memory (1.3.7)
Throw when querying non-scalar objects without a selection set.
Issue #4025
PR #4038
Work around spec non-compliance of
Map#setandSet#addin IE11.Issue #4024
PR #4012
v2.4.3Add additional checks to make sure we don't try to set the network status
of queries in the store, when the store doesn't exist.
@i6mi6 in #3914
Documentation updates.
@shanonvl in #3925
@ojh102 in #3920
@Bkucera in #3919
@j4chou in #3915
@billfienberg in #3886
@TLadd in #3884
The
ObservableQueryclass now makes a deep clone oflastResultwhenfirst received, so that the
isDifferentResultlogic will not beconfused if the result object is modified later.
Issue #3992
PR #4032
Apollo Cache In-Memory (1.3.6)
Optimize repeated
apollo-cache-inmemoryreads by caching partial queryresults, for substantial performance improvements. As a consequence, watched
queries will not be rebroadcast unless the data have changed.
PR #3394
Include root ID and fragment matcher function in cache keys computed by
StoreReader#executeStoreQueryandexecuteSelectionSet, and workaround bugs in the React Native
MapandSetpolyfills.PR #3964
React Native PR #21492 (pending)
The
apollo-cache-inmemorypackage now allowsgraphql@^14.0.0as apeer dependency.
Issue #3978
The
apollo-cache-inmemorypackage now correctly broadcasts changeseven when the new data is
===to the old data, since the contents ofthe data object may have changed.
Issue #3992
PR #4032
Apollo GraphQL Anywhere (4.1.20)
graphql-anywherefilterfunction generic (typescript).@minznerjosh in #3929
Apollo Utilities (1.0.22)
fclonepackage has been replaced with a customcloneDeepimplementation that is tolerant of cycles, symbol properties, and
non-enumerable properties.
PR #4032
Apollo Boost (0.1.17)
Issue #3910
PR #3932
Apollo Cache (1.1.18)
v2.4.2Apollo Client (2.4.2)
@hwillson in #3883
clearStoremethod has been added, that will remove all data fromthe store. Unlike
resetStore, it will not refetch active queries afterremoving store data.
@hwillson in #3885
Apollo Utilities (1.0.21)
cloneDeepimplementation withfclone, to avoid crashing whenencountering circular references.
@hwillson in #3881
Apollo Boost (0.1.16)
Apollo Cache (1.1.17)
Apollo Cache In-Memory (1.2.10)
Apollo GraphQL Anywhere (4.1.19)
v2.4.1Apollo Client (2.4.1)
mutate'srefetchQueriesoption now allows queries to include a customcontextoption. Thiscontextwill be used when refetching the query.For example:
The
CUSTOMER_MESSAGES_QUERYabove will be refetched usingcontext.Normally queries are refetched using the original context they were first
started with, but this provides a way to override the context, if needed.
@hwillson in #3852
Documentation updates.
@hwillson in #3841
Apollo Boost (0.1.15)
testing, etc.
@hwillson in #3817
Apollo Cache (1.1.16)
testing, etc.
@hwillson in #3817
Apollo Cache In-Memory (1.2.9)
testing, etc.
@hwillson in #3817
Apollo Utilities (1.0.20)
testing, etc.
@hwillson in #3817
Apollo GraphQL Anywhere (4.1.18)
testing, etc.
@hwillson in #3817
v2.4.0Apollo Client (2.4.0)
errorhandler on your subscription observer, it will now be called when an error
comes back in a result, and the
nexthandler will be skipped (similar tohow we're handling errors with mutations). Previously, the error was
just passed in the result to the
nexthandler. If you don't have anerrorhandler defined, the previous functionality is maintained, meaningthe error is passed in the result, giving the next handler a chance to deal
with it. This should help address backwards compatibility (and is the reason
for the minor version bumo in this release).
@clayne11 in #3800
optimisticparam to be passed intoApolloClient.readQueryandApolloClient.readFragment, that when set totrue, will allowoptimistic results to be returned. Is
falseby default.@jay1337 in #2429
@joshribakoff in #3713
.npmignore, so they're taken intoconsideration when publishing via lerna.
@hwillson in #3828
@toolness in #3804
@pungggi in #3798
@lorensr in #3748
@joshribakoff in #3730
@yalamber in #3819
@pschreibs85 in #3812
@msreekm in #3808
@kamaltmo in #3806
@lorensr in #3739
@brainkim in #3680
Apollo Cache In-Memory (1.2.8)
console.warnregarding fragment matching error message.@combizs in #3701
Apollo Boost (0.1.14)
Apollo Cache (1.1.15)
Apollo Utilities (1.0.19)
Apollo GraphQL Anywhere (4.1.17)
v2.3.8Apollo Client (2.3.8)
graphqlpeer dependency to cover explicit minor ranges.Since the ^ operator only covers any minor version if the major version
is not 0 (since a major version of 0 is technically considered development by
semver 2), the current ^0.11.0 || ^14.0.0 graphql range doesn't cover
0.12._ or 0.13._. This fixes the
apollo-client@X has incorrect peer dependency "graphql@^0.11.0 || ^14.0.0"errors that people might haveseen using
graphql0.12.x or 0.13.x.@hwillson in #3746
setVariablesinternal API status.@PowerKiKi in #3692
ApolloClient.queryManagertyping as it may beundefined.@danilobuerger in #3661
no-cachefetch policy with subscriptions prevents datafrom being cached.
@hwillson in #3773
no-cachefetch policy.@hwillson in #3777
@hwillson in #3750
@hwillson in #3754
@TheMightyPenguin in #3725
@bennypowers in #3668
@hwillson in #3762
@chentsulin in #3688
@chentsulin in #3687
@ardouglass in #3645
@hwillson in #3764
@hwillson in #3767
@hwillson in #3774
@hwillson in #3779
Apollo Boost (0.1.13)
Apollo Cache In-Memory (1.2.7)
Apollo Cache (1.1.14)
Apollo Utilities (1.0.18)
Apollo GraphQL Anywhere (4.1.16)
v2.3.7Apollo Client (2.3.7)
QueryManager'sgetQueryWithPreviousResultmethod included an invalidvariablesreturntype in the auto-generated
core/QueryManager.d.tsdeclaration file. Thetype definition had a locally referenced path, that appears to have been
caused by the typescript compiler getting confused at compile/publish time.
getQueryWithPreviousResultreturn types are now excplicity identified,which helps Typescript avoid the local type reference. For more details,
see #3729.
@hwillson in #3731
Apollo Boost (0.1.12)
v2.3.6Apollo Client (2.3.6)
@ananth99 in #3599
@hwillson in #3635
@JakeDawkins in #3642
@hwillson in #3644
@gbau in #3644
@chentsulin in #3608
@MikaelCarpenter in #3609
@Gamezpedia in #3612
@jinxac in #3647
@abernix in #3705
@dandv in #3703
@hwillson in #3580
graphqlpeerDependenciesto handle 14.x versions.@ivank in #3598
@mvestergaard in #3588
awaitRefetchQueriesconfig option to the Apollo Clientmutatefunction, that when set totruewill wait for allrefetchQueriesto be fully refetched, before resolving the mutationcall.
awaitRefetchQueriesisfalseby default.@jzimmek in #3169
Apollo Boost (0.1.11)
fetchto be given as a configuration option toApolloBoost.@mbaranovski in #3590
apollo-boostApolloClientconstructor now warns about unsupportedoptions.
@quentin- in #3551
Apollo Cache (1.1.13)
Apollo Cache In-Memory (1.2.6)
__typenameandidproperties todataIdFromObjectparameter(typescript)
@jfurler in #3641
dataIdFromObjectconsidering returned 0 values tobe falsy, instead of being a valid ID, which lead to the store not being
updated properly in some cases.
@hwillson in #3711
Apollo Utilities (1.0.17)
Apollo GraphQL Anywhere (4.1.15)
graphql-anywhere's filter utility.@jsweet314 in #3591
Cannot convert object to primitive valueerror that was showing upwhen attempting to report a missing property on an object.
@benjie in #3618
v2.3.5Apollo Client (2.3.5)
Apollo Boost (0.1.10)
Apollo Cache (1.1.12)
Apollo Cache In-Memory (1.2.5)
Apollo Utilities (1.0.16)
Apollo GraphQL Anywhere (4.1.14)
v2.3.4Apollo Client (2.3.4)
QueryOptionsinterface, to make sure it can be used by otherprojects (like
apollo-angular).defaultOptionsparam, that preventedquerydefaults from passing typechecks.
(@hwillson in #3585)
Apollo Boost (0.1.9)
Apollo Cache (1.1.11)
Apollo Cache In-Memory (1.2.4)
Apollo Utilities (1.0.15)
Apollo GraphQL Anywhere (4.1.13)
v2.3.3Apollo Client (2.3.3)
variables:
ObservableQuery<TData, TVariables>(@excitement-engineer in #3140)
(@mvestergaard in #3541)
QueryOptionsinterface thatis now used by
ApolloClient.queryoptions, instead of the previousWatchQueryOptionsinterface. This helps reduce confusion (especiallyin the docs) that made it look like
ApolloClient.queryacceptedApolloClient.watchQueryonly options, likepollingInterval.(@hwillson in #3569)
Apollo Boost (0.1.8)
cacheto be given as a configuration option toApolloBoost.(@dandean in #3561)
headersandcredentialsto be passed in as configurationparameters to the
apollo-boostApolloClientconstructor.(@rzane in #3098)
Apollo Cache (1.1.10)
(@mvestergaard in #3541)
Apollo Cache In-Memory (1.2.3)
(@mvestergaard in #3541)
resultFields[ID_KEY].(@benjamn in #3544)
(@benjamn in #3553)
Apollo Utilities (1.0.14)
getStoreKeyNamenow leverage a moredeterministic approach to handling JSON based strings. This prevents store
key names from differing when using
argslike{ prop1: 'value1', prop2: 'value2' }and{ prop2: 'value2', prop1: 'value1' }.(@gdi2290 in #2869)
hasOwnPropertycheck indeepFreeze.(@benjamn in #3545)
Apollo GraphQL Anywhere (4.1.12)
v2.3.2Apollo Client (2.3.2)
cache-and-networkfetch policy(@dastoori in #3372)
updateQuerymethod passed toObservableQuery.fetchMorewas receiving the original query variables,instead of the new variables that it used to fetch more data.
(@abhiaiyer91 in #3500)
Object.setPrototypeOf()not working on JSC(Android), by instead setting the
prototypeofthismanually.(@seklyza in #3306)
QueryStore.initQueryandQueryStore.markQueryResultdon't try to set the network status of afetchMoreForQueryIdquery, if it does not exist in the store. This washappening when a query component was unmounted while a
fetchMorewas stillin flight.
(@conrad-vanl in #3367, @doomsower in #3469)
Apollo Boost (0.1.7)
Apollo Cache (1.1.9)
Apollo Cache In-Memory (1.2.2)
(@abhiaiyer91 in #3507)
arrays.
(@dferber90 in #3422)
Apollo Utilities (1.0.13)
maybeDeepFreezea little more defensive, by always usingObject.prototype.hasOwnProperty(to avoid cases where the object beingfrozen doesn't have its own
hasOwnProperty).(@jorisroling in #3418)
(@brunorzn in #3444)
Apollo GraphQL Anywhere (4.1.11)
(@hwillson in #3454)
apollostack/graphql-tag
v2.10.0Compare Source
graphql@14by timsuchanek in #210, #211v2.9.2Compare Source
v2.9.1Compare Source
v2.9.0Compare Source
experimentalFragmentVariablescompatibility by lucasconstantino in #167v2.8.0Compare Source
graphqlto ^0.13, support testing all compatible versions jnwng inPR #156
PR #154
v2.7.3Compare Source
v2.7.1Compare Source
v2.7.0Compare Source
v2.6.1Compare Source
graphql@^0.12.0as peerDependency jnwngaddressing #134
v2.6.0Compare Source
PR #122
v2.5.0Compare Source
PR #124
v2.4.2Compare Source
v2.4.1Compare Source
v2.4.0Compare Source
PR #99
v2.3.0Compare Source
PR #98
v2.2.2Compare Source
PR #95
v2.2.1Compare Source
PR #89
v2.2.0Compare Source
graphqlpeer dependency to ^0.10.0 dotansimha inPR #85
v2.1.0Compare Source
gqlas a function matthewerwin inPR #66
PR #72
PR #52
graphql-tag/loaderby properly stringifying GraphQL Source jnwng inPR #65
v2.0.0Compare Source
Restore dependence on
graphqlmodule abhiaiyer91 inPR #46 addressing
#6
graphqlas apeerDependency
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.