Thomas Suckow

They are intending to keep the requirement that onComplete, et. al needs to be memoized. Since Apollo Client 3 is react hook based, that requirement makes sense (Rules of Hooks)....

I cannot for the life of me find what I swear was a dev or a commit stating they intentionally changed the behavior. Regardless, When using `useQuery` the options object...

Yep. Which when the cache strategy is set to network-only causes an infinite loop if one of them isn't memoized.

I'm working on a charting "library" and was finding that immutable scales are pretty much a necessity to keep my sanity. Especially as I implement zooming which has to muck...

I cannot reproduce this in 2.10.1 / 1.6.1 Close?

Right click in the editor and select "Reset Scala Parser" and then switch to another source file and switch back.

```typescript declare module "@mixmaxhq/promise-pool" { interface PromisePoolOptions { /** * default: 4 */ numConcurrent?: number; /** * default: 1 */ maxPending?: number; } class PromisePool { constructor(config?: PromisePoolOptions); start(fn: (...args:...

So that should work if we called this library in the resolver of the thing being aliased. In our setup we have an ElasticSearch database that accepts complex queries returning...

Query: ```graphql query getSearch($query: JSON!) { search(query: $query) { things(limit: 1000, type: "dog") { id } cat: things(limit: 500, type: "cat") { id } } } ``` Generated Tree (note...

To be honest, I reach in and take the _tree and don't use your selectors. I use lodash/fp/get to access things. ```javascript if( get('things.$args.type')(tree._tree) ) { ... } ``` Though...