Skip to main content

TypeScript compiler trick

Last week I showed you how to use Pattern Matching and more specifically the Type Pattern in TypeScript. I used a set of commands:

with a corresponding command handler as an example:

While reading the following article I noticed that a TypeScript compiler trick was mentioned to further improve the type safety of our code. In the article the following code was used:

As it wasn’t immediately clear to me what this code does exactly I decided to write a blog post about it.

Explaining the magic

The TypeScript code above defines a generic type alias named CommandTypeOf. This alias takes a type parameter T that must extend from a type named Command. The resulting type of CommandTypeOf<T> is the type of the type property of T.

In simpler terms, this code is used to extract the type of the type property from our Command type. You can use CommandTypeOf<CreateUserCommand> to get the type 'createUser', which is the type of the type property in CreateUserCommand.

This is a powerful pattern for creating type-safe command handling systems, where the type of the command can be used to determine its behavior at compile time.

Let’s see it in action

I’ve created an CommandProcessor interface that can be implemented to link a Command to a CommandHandler. As you can see in the code above I’m using the CommandTypeOf<T> to limit the types that can be provided. 

If we now want to call the handle method you see that the compiler only offers us the supported command types:

So if we call the CommandProcessor like this, it will work:

But if we want to provide an unknown command type, the compiler will complain:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...