Frontend

I was looking at google's new node SDK for gemini.

I like this "disjoint types" pattern. A very good way to make your TypeScript very readable + meaningful, I have used something similar, but not with the "never" trick.

We made a change today in Axflow that follows this pattern 💪

Building https://srcbook.com // creator of the https://blockchainsmokers.xyz

We made a change today in Axflow that follows this pattern 💪
https://github.com/axflow/axflow/pull/104/files

typescript

Looks like we need a /typescript channel!

/frontend dev・founder/decentralized data wrangler /blockhead・ritual.net・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx・x.com/darryl__yeo

The caveat with this “optional never” approach is that it still allows the property to be set to undefined.

This may not be what you want if your logic depends on the presence or non-presence of a property, i.e. using the JavaScript “in” operator.

I usually do this with protobufs' oneof

Didn't know about `never`. Nice feature.

When you manipulate a Part, it's always either a TextPart or a InlineDataPart.

The cheap way to describe this is:
Part {
  text?: string;
  inlineData?: thing;
}

But this isn't as helpful: it doesn't tell you that it's strictly one or the other.

Discriminated Unions are a good feature, if only typescript had a better way to actually identify the type (I know it’s javascript’s fault it can’t, but I still wish it did)