Stephen Haberman

Disclaimer I'm sure this is too naive to be useful, but my "if I could wave a magic wand" dream would be to have deno auto-manage a "each time your...

FWIW I am just starting to use polly for a workflow of: 1) Record with a secret token (to get back valid responses from vendor that requires auth), 2) take...

@zorji hey! Nope, I'd be fine with just `ExactDeep`. Really great to here you're working on this. FWIW I copied your current version into a project that is perhaps a...

I also get this fun guy:  :-) However it must be something esoteric with our project-specific `DeepPartialOrNull`, as it works with a vanilla `DeepPartial`, which is great: ``` it("works...

@vimmerru > load level-2 or level-3 references I'll selfishly be brief (ish), and link to something like: https://medium.com/@__xuorig__/the-graphql-dataloader-pattern-visualized-3064a00f319f (which is technically about GraphQL, but applies even to a non-GraphQL endpoint...

Fwiw @darkbasic aren't we essentially reimple Harusa or Postgraphile at that point? I.e. info-based resolution into a single query (which they both do afaiu) generally requires your gql schema and...

> doesn't try to make a single big query Ah gotcha, sorry, I was scanning your PR on mobile and saw the term "single big query" and latched on to...

Thanks for keeping this issue open! FWIW I avoided this by staying on `@emotion/react` `v11.1.4` instead of `v11.4.1`, so we didn't have to go all the way back to `v10`.

@Andarist well, in retrospect, the older v11 really did seem to make the `tsc` "Interpolation vs. InterpolationWithTheme" compile error go away, but I'm still not out of the [storybook emotion...

Thanks @Andarist ! In my case, somehow `npm` decided to dedup storybook's `@emotion/core@10` dependency on `@emotion/cache` to `@emotion/cache@11` (which ended up causing https://github.com/emotion-js/emotion/issues/1826): ``` $ npm ls @emotion/cache [email protected] /home/stephen/homebound/internal-frontend...