David Sheldrick

Ah yeah! That's an open issue https://github.com/Microsoft/TypeScript/issues/24929 — I left this out of my talk but should probably have included it in the blog post as another caveat. Unfortunately the...

Hey @bdurrani! 👋 You're right. That's an open issue: TS can't type-check the return value of functions with conditional return types defined in terms of type parameters. See the link...

I suppose the problem is that TypeScript can't yet narrow the types of two independent variables, even if their types are codependent. One thing I might be tempted to try...

@hienqnguyen Yeah I see what's going on there. That's the correct behaviour. Let me break it down: `FuncType` ends up being a union of the two function signatures in `myFunc`....

Hi @marzelin :wave: Thanks for the feedback! I will address your concerns individually > No, we cannot use conditional types here since the signature is invalid. It's not a bug,...

@vicke4 Awesome! A few people have sent me solutions to that challenge and I'm amazed that they've all been different! Yours is very neat 💯

> The one caveat is that instead of a node 'silently' being null (and a client possibly already handling it properly), there will now be that 'Cannot return null for...

@mzikherman I've tested this out locally with force and eigen and it all seems good, everything works as before. The one problem is that reaction is on an older version...

I forgot to add an update here, thanks for the bump @alloy 😅 This PR is still blocked by force. I tried to upgrade relay in force after reaction was...

yeah I updated to the latest versions of everything. Not sure where the failure is but the symptom is that in ```graphql someConnection { edges { node { __typename }...