Matt Pocock Profile picture
Mar 2, 2023 18 tweets 6 min read Read on X
satisfies in TypeScript has been out for a little while now.

Overall, it's been a success - but it's starting to cause some confusion.

Let's clear it up. const obj = {} satisfies Record<string, string>;  // Propert
satisfies has added yet another tool to the TypeScript user's toolkit.

There are now _three_ ways to assign types to values.

First, there's the humble 'colon annotation'.

This concept isn't really given a name in the TS docs, so I'll use this slightly medical name.

This lets you say 'this variable is always this type'. const obj: Record<string, string> = {};  obj.id = "123&
When you use a colon annotation, you're _declaring_ that the variable is that type.

That means that the thing you assign to the variable _must_ be that type. // Type 'number' is not assignable to type 'string'. const s
This means you can actually give a variable a type that's _wider_ than the one you initially assign.

This is useful when you want to have a default which might later be reassigned. let id: string | number = "123";  if (typeof numer
But colon annotations come with an edge-case downside.

When you use one, the type BEATS the value. That means that if you declare a wider type than you want, you're stuck with the wider type.

In this example, you don't get autocomplete on the routes object. const routes: Record<string, {}> = {   "/": {},
This is the problem satisfies was designed to solve.

When you use satisfies, the value BEATS the type. This means it infers the narrowest possible type, not the wider type you specify. const routes = {   "/": {},   "/users":
satisfies also protects you from specifying the wrong thing inside your config object.

So, colon annotations and satisfies are equally safe. const routes = {   // Type 'null' is not assignable to type
The third way you can assign types to variables is the 'as' annotation.

Unlike satisfies and colon annotations, 'as' annotations let you lie to TypeScript. type User = {   id: string;   name: {     first: string;
This has some limits - you can add properties to objects, but you can't convert between basic types.

For instance, you can't force TypeScript to convert a string into a number...

...except if you use the monstrous 'as-as'. // Conversion of type 'string' to type 'number' // may be a
Sometimes, 'as' is needed. For instance, when you're converting an object to a known type. type User = {   id: string;   name: string; };  // The user
But if you're using 'as' as your default way to annotate variables, that's almost certainly wrong.

The code below might look safe, but as soon as you add another property to the User type, the defaultUser will be out of date - and won't error. type User = {   id: string;   name: string; };  const defaul
There's actually a secret _fourth_ way to give a type to a variable.

Don't.

TypeScript does an amazing job at inferring types for your variables.

Most of the time, you won't need to type your variables. const routes = {   "/": {},   "/users":
So, we've got FOUR ways of assigning a type to a variable.

- colon annotations
- satisfies
- as annotations
- not annotating and inferring it
The mistake I'm seeing a lot of devs make with the release of 'satisfies' is to use it as their new default.

This is fine for simple cases like this: type User = {   id: string;   name: string; };  const defaul
But most of the time, the times you want to assign a type to a variable are when you _want_ the type to be wider.

For instance, this case. If we used satisfies here, you wouldn't be able to assign numericId to id. // colon annotation  let id: string | number = "123&quo
So - satisfies shouldn't be your default. It's for edge cases. It should be for when:

- You want the EXACT type of the variable, not the WIDER type.
- The type is complex enough that you want to make sure you didn't mess it up
If you dug this thread, my TypeScript course just launched - and it's on sale for another week.

Thanks for reading! ❤️❤️

totaltypescript.com

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Matt Pocock

Matt Pocock Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @mattpocockuk

Apr 9
I've just been reading the Agent2Agent technical docs - Google's new protocol for agent to agent communication.

You know what that means. Let's diagram them: Image
Agents can be discovered by a public 'card' they expose via http. Image
There are three 'actors' in an A2A system. The user, the client, and the server. Not too tricky. Image
Read 5 tweets
Apr 9
Some notes on Cursor vs VSCode's new agent mode:
I'm currently working on a course where each lesson is a prompt, and you build a complex application from ~50 prompts.

This gives me a pretty gnarly eval for testing agent mode.

I've been using Cursor to build the course, but I tried VSCode instead.

How did it do?
Overall, VSCode performed well. The code produced by both was pretty decent, and they were comparable in terms of speed.

VSCode's agent was able to keep up with Cursor in terms of outputted code, with an important exception:
Read 8 tweets
Mar 25
Ohhhhhh I think I've found an AI writing flow I'm happy with

Need to iterate on it before I write about it more, but it's really working.
Essentials are:

1. Create a big multi-step plan for the article, including checkboxes. On the current article I'm working on, it's 16+ steps.
2. For each step, ask it for 3 different plans for how to write the section. Give the section a target word count.
3. Get it to apply this to the document.
4. Do passes for paragraph length and section headings before even reading the paragraphs.
5. Do passes for writing style, analogies.
6. Get it to rewrite things in lists if needed.
Read 7 tweets
Mar 7
MCP has ALREADY become an overloaded term.

Let's break it down into clients, servers and protocols: Image
MCP is built out of three ideas.

You have a client, a server, and a protocol to connect them together. Let's define each of them in turn.
The server is the thing that chats to the API's.

It can be on a remote server (i.e. in the cloud), or on your local system.

It contains all the code needed to actually take actions on the systems it talks to - sending Slack messages, creating files etc. Image
Read 7 tweets
Mar 6
Lots of folks feeling FOMO about MCP.

Here's the problem it solves: Image
Image
If you want to get your LLM to do useful things in the world, you will quickly hit a problem.

All the useful things in the world, like Slack, GitHub, or even your local filesystem, provide their own unique API to access them.
So, you end up writing a ton of code to glue your LLM and those API's together.

Want to add a new tool? That's more glue code. Grim.
Read 6 tweets
Oct 1, 2024
z.strict() fixed a nasty bug for me this morning.

You should probably be using it on most of the schemas that handle outside data.

Here's the bug 🧵 Image
I had a form where I was marking the date a post was posted. I was expecting a key of `postedAt`, with an optional datetime. Image
Except, in my form, I had gotten the `name` field wrong: Image
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(