-
Notifications
You must be signed in to change notification settings - Fork 20
Update dependency apollo-client to v2 - autoclosed #122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@renovate
renovate
bot
force-pushed
the
renovate/apolloclient-monorepo
branch
3 times, most recently
from
June 20, 2018 01:30
2dca32f
to
e7a564c
Compare
@renovate
renovate
bot
force-pushed
the
renovate/apolloclient-monorepo
branch
2 times, most recently
from
July 25, 2018 01:38
d32f763
to
d109fe4
Compare
@renovate
renovate
bot
force-pushed
the
renovate/apolloclient-monorepo
branch
from
August 9, 2018 12:13
d109fe4
to
446d5f8
Compare
@renovate
renovate
bot
force-pushed
the
renovate/apolloclient-monorepo
branch
from
August 17, 2018 14:07
446d5f8
to
79bcbee
Compare
@renovate
renovate
bot
force-pushed
the
renovate/apolloclient-monorepo
branch
from
August 26, 2018 16:33
79bcbee
to
086755d
Compare
@renovate
renovate
bot
changed the title
(削除) Update dependency apollo-client to v2 (削除ここまで)
(追記) Update dependency apollo-client to v2 - autoclosed (追記ここまで)
Aug 27, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Uh oh!
There was an error while loading. Please reload this page.
This Pull Request updates dependency
apollo-client
(source) fromv1.9.3
tov2.4.1
Release Notes
v2.4.1
Compare Source
Apollo Client (2.4.1)
mutate
'srefetchQueries
option now allows queries to include a customcontext
option. Thiscontext
will be used when refetching the query.For example:
The
CUSTOMER_MESSAGES_QUERY
above 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.0
Compare Source
Apollo Client (2.4.0)
error
handler on your subscription observer, it will now be called when an error
comes back in a result, and the
next
handler will be skipped (similar tohow we're handling errors with mutations). Previously, the error was
just passed in the result to the
next
handler. If you don't have anerror
handler 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
optimistic
param to be passed intoApolloClient.readQuery
andApolloClient.readFragment
, that when set totrue
, will allowoptimistic results to be returned. Is
false
by 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.warn
regarding 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.8
Compare Source
Apollo Client (2.3.8)
graphql
peer 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
graphql
0.12.x or 0.13.x.@hwillson in #3746
setVariables
internal API status.@PowerKiKi in #3692
ApolloClient.queryManager
typing as it may beundefined
.@danilobuerger in #3661
no-cache
fetch policy with subscriptions prevents datafrom being cached.
@hwillson in #3773
no-cache
fetch 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.7
Compare Source
Apollo Client (2.3.7)
QueryManager
'sgetQueryWithPreviousResult
method included an invalidvariables
returntype in the auto-generated
core/QueryManager.d.ts
declaration file. Thetype definition had a locally referenced path, that appears to have been
caused by the typescript compiler getting confused at compile/publish time.
getQueryWithPreviousResult
return 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.6
Compare Source
Apollo 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
graphql
peerDependencies
to handle 14.x versions.@ivank in #3598
@mvestergaard in #3588
awaitRefetchQueries
config option to the Apollo Clientmutate
function, that when set totrue
will wait for allrefetchQueries
to be fully refetched, before resolving the mutationcall.
awaitRefetchQueries
isfalse
by default.@jzimmek in #3169
Apollo Boost (0.1.11)
fetch
to be given as a configuration option toApolloBoost
.@mbaranovski in #3590
apollo-boost
ApolloClient
constructor now warns about unsupportedoptions.
@quentin- in #3551
Apollo Cache (1.1.13)
Apollo Cache In-Memory (1.2.6)
__typename
andid
properties todataIdFromObject
parameter(typescript)
@jfurler in #3641
dataIdFromObject
considering 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 value
error that was showing upwhen attempting to report a missing property on an object.
@benjie in #3618
v2.3.5
Compare Source
Apollo 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.4
Compare Source
Apollo Client (2.3.4)
QueryOptions
interface, to make sure it can be used by otherprojects (like
apollo-angular
).defaultOptions
param, that preventedquery
defaults 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.3
Compare Source
Apollo Client (2.3.3)
variables:
ObservableQuery<TData, TVariables>
(@excitement-engineer in #3140)
(@mvestergaard in #3541)
QueryOptions
interface thatis now used by
ApolloClient.query
options, instead of the previousWatchQueryOptions
interface. This helps reduce confusion (especiallyin the docs) that made it look like
ApolloClient.query
acceptedApolloClient.watchQuery
only options, likepollingInterval
.(@hwillson in #3569)
Apollo Boost (0.1.8)
cache
to be given as a configuration option toApolloBoost
.(@dandean in #3561)
headers
andcredentials
to be passed in as configurationparameters to the
apollo-boost
ApolloClient
constructor.(@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)
getStoreKeyName
now leverage a moredeterministic approach to handling JSON based strings. This prevents store
key names from differing when using
args
like{ prop1: 'value1', prop2: 'value2' }
and{ prop2: 'value2', prop1: 'value1' }
.(@gdi2290 in #2869)
hasOwnProperty
check indeepFreeze
.(@benjamn in #3545)
Apollo GraphQL Anywhere (4.1.12)
v2.3.2
Compare Source
Apollo Client (2.3.2)
cache-and-network
fetch policy(@dastoori in #3372)
updateQuery
method passed toObservableQuery.fetchMore
was 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
prototype
ofthis
manually.(@seklyza in #3306)
QueryStore.initQuery
andQueryStore.markQueryResult
don't try to set the network status of afetchMoreForQueryId
query, if it does not exist in the store. This washappening when a query component was unmounted while a
fetchMore
was 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)
maybeDeepFreeze
a 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)
v2.3.1
Compare Source
v2.3.0
Compare Source
v2.2.8
Compare Source
v2.2.7
Compare Source
v2.2.6
Compare Source
v2.2.5
Compare Source
v2.2.4
Compare Source
v2.2.3
Compare Source
v2.2.2
Compare Source
v2.2.1
Compare Source
v2.2.0
Compare Source
v2.1.0
Compare Source
v2.0.4
Compare Source
v2.0.3
Compare Source
v2.0.2
Compare Source
v2.0.1
Compare Source
v2.0.0
Compare Source
This PR has been generated by Renovate Bot.