profile
viewpoint

sergioramos/jsctags 475

jsctags generator using tern

timkendrick/monaco-editor 58

CommonJS/Webpack compatible Monaco editor

timkendrick/memoize-bind 25

Memoized function binding for React

timkendrick/memoize-weak 21

Garbage-collected memoizer for variadic functions

timkendrick/doppelganger 15

Run Backbone.js apps on a Node.js server

timkendrick/monaco-editor-loader 9

Webpack loader for the Monaco editor

timkendrick/mock-cli 5

CLI capture tool for testing command-line apps

timkendrick/factory 2

Quick and easy template scaffolding for Node

timkendrick/angular-charts 1

Semantic charts for AngularJS

timkendrick/babel-preset-vscode 1

Babel preset for Visual Studio Code modules

startedgigamonkey/monorepoize

started time in a month

issue openedapollographql/apollo-client

watchQuery with pollInterval ignores no-cache fetchPolicy

Currently, when executing a watchQuery with a pollInterval and the fetchPolicy: 'no-cache' option, the caching option is overridden internally within Apollo to network-only, causing data to be written to the cache despite the no-cache fetch policy.

Intended outcome:

client.watchQuery({
  query,
  pollInterval: 1000,
  fetchPolicy: 'no-cache', // No objects should be written to the cache
}).valueChanges.subscribe(...);

Actual outcome: The cache .write() method is called with the results of the query

How to reproduce the issue: See 'Intended outcome' section

Versions

  System:
    OS: macOS Mojave 10.14.6
  Binaries:
    Node: 12.14.0 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.13.4 - /usr/local/bin/npm
  Browsers:
    Chrome: 81.0.4044.113
    Firefox: 61.0.2
    Safari: 13.1
  npmPackages:
    @apollo/client: 3.0.0-beta.44 => 3.0.0-beta.44

created time in a month

fork timkendrick/openfin-cli

Launch the OpenFin runtime

fork in a month

startedmaxchehab/phelia

started time in a month

more