Eloy Durán

And what’s the main reason(s) to avoid requesting a total count?

But yeah, reading my own comment with a fresh mind, I come back to my original comment and agree with @yuki24 that this couldn’t work if the actual available amount...

The main reason I asked for a motivation is that, assuming it’s indeed meant as optimization, I for one don’t know if it’s more costly to return a count or...

This makes sense and based on what @broskoski tells me this shouldn’t be too hard. @craigspaeth can you pick this up?

Oh yes please! 🙏🏽

I’ve been seeing that too FWIW. I attributed it to the vscode update I had installed.

Is it related to the auto attaching?

A ✨ Ruby option: ```ruby artist do for_sale_artworks > artworks(for_sale: true) not_for_sale_artworks > artworks(for_sale: false) end ``` But may be _too_ magical 😊

> One offender is this call where we create a new fragment document object every time (note: `fragment: {` is always a new object): > > https://github.com/microsoft/graphitation/blob/cc843406967da7c964bd5c68e79e1cc3f1b234f5/packages/apollo-react-relay-duct-tape/src/storeObservation/nodeFromCacheFieldPolicy.ts#L42-L52 This one is...

Also see this post by @andrewingram https://andrewingram.net/posts/optimising-your-graphql-request-waterfalls/