ObservableQuery

result(): Promise<ApolloQueryResult>

(src/core/ObservableQuery.ts, line 162)

getCurrentResult(saveAsLastResult): ApolloQueryResult<>

(src/core/ObservableQuery.ts, line 196)

Arguments

refetch(variables): Promise<ApolloQueryResult>

(src/core/ObservableQuery.ts, line 319)

Update the variables of this observable query, and fetch the new results. This method should be preferred over setVariables in most use cases.

Arguments

setOptions(newOptions): Promise<ApolloQueryResult>

(src/core/ObservableQuery.ts, line 490)

Arguments

setVariables(variables): Promise<>

(src/core/ObservableQuery.ts, line 517)

This is for internal use only. Most users should instead use refetch in order to be properly notified of results even when they come from cache.

Update the variables of this observable query, and fetch the new results if they've changed. If you want to force new results, use refetch.

Note: the next callback will not fire if the variables have not changed or if the result is coming from cache.

Note: the promise will return the old results immediately if the variables have not changed.

Note: the promise will return null immediately if the query is not active (there are no subscribers).

Arguments

fetchMore(fetchMoreOptions): Promise<ApolloQueryResult>

(src/core/ObservableQuery.ts, line 360)

Arguments

updateQuery(mapFn): any

(src/core/ObservableQuery.ts, line 543)

Arguments

startPolling(pollInterval): any

(src/core/ObservableQuery.ts, line 572)

Arguments

stopPolling(): any

(src/core/ObservableQuery.ts, line 577)

subscribeToMore(options): (Anonymous function)

(src/core/ObservableQuery.ts, line 443)

NetworkStatus

(src/core/networkStatus.ts, line 4)

The current status of a query’s execution in our system.

ApolloQueryResult

(src/core/types.ts, line 135)

Properties