-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
WIP: replace noFetch and forceFetch with fetch policy #1371
Conversation
src/core/watchQueryOptions.ts
Outdated
* - cache-only: return result from cache if avaiable, fail otherwise. | ||
* - network-only: return result from network, fail if network call doesn't succeed. | ||
*/ | ||
export type FetchPolicy = 'cache-first' | 'cache-and-network' | 'network-first' | 'cache-only' | 'network-only'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Until we implement the others we should make this have only the ones we actually support, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I'm still planning to implement the others tomorrow :)
@@ -310,9 +310,10 @@ export class ObservableQuery<T> extends Observable<ApolloQueryResult<T>> { | |||
this.stopPolling(); | |||
} | |||
|
|||
// If forceFetch went from false to true or noFetch went from true to false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LOL this comment
tiny little steps
docs update will happen with Caleb's PR.