@OnkelTem everything looks to be working as expected in the TS playground links you provided. In the first one, there are no type errors as expected, sinceFooDerived["foo"] andFoo["foo"] are bothstrings. In the second there are type errors becauseFoo["foo"] is anumber andFooDerived["foo"] is astring.

I'm also seeing intellisense when creating a model, and also when referencing properties on a created model:

Do you have a more complete example where things aren't working?

Intellisense works for an existing model, while I speak about creatingthe model itself.

Instead we're given with a TypeScript API, whereFoo is already defined and we create a model for it, so we type:

t.model('Foo', {...

and get nothing, because model isn't typed.

In the second there are type errors because Foo["foo"] is a number and FooDerived["foo"] is a string.

Yeah, but that's a result of an investigation and not what is displayed in the error message.

Oh, I think I understand what you're asking now. You type

t.model('Foo',{

And then ask for intellisense to show you options. There aren't meant to be options there by default, but you happen to already have an existing interface and want to have MST adhere to that. I don't think there's a natural solution that MST can give you (maybe you have some suggestions?), but I can see two options that you could use without any changes to MST:

Usesatisfies

The type of a properties blob is pretty complicated, so I don't think you can easily adapt some arbitrary interface to it. If you happen to only be mapping keys to primitive values, you could probably do something similar to what we do internally (which MST could expose):

Alternatively, if you only care about the keys, you could do something like this:

types.model("Foo",{}satisfiesRecord<keyofFoo,any>)

That's kind of gross though, so maybe this would be better:

import{types,IType}from"mobx-state-tree";typeFoo={foo:string;};constMyModelFoo=types.model("Foo",{foo:types.string,})satisfiesIType<any,Foo,any>;

Adjust your type assertions

If your interface is meant to match an instance/snapshot of a model, which I'm guessing it is given your playground links, I would recommend something close to what you had in TS playground:

import{types,SnapshotOut}from"mobx-state-tree";typeFoo={foo:number;};constMyModelFoo=types.model("Foo",{foo:types.string,});typeFooDerived=SnapshotOut<typeofMyModelFoo>typeTest<TextendsFoo>="yes";type_=Test<FooDerived>

That will give you something a little more meaningful in the error message at the cost of having to write these out for every model:

I see, Jason! Many thanks :)

As for the ideas - yeah, I've got one:#2239 :)

@thegedge really nailed it here, but I understand where you're coming from,@OnkelTem.

I'll add that I've seen thesatisfies approach work pretty well. I did a bit of consulting with a team that used it for a similar use case as yours, and I thought it was clever.

I'll read through#2239 and think it over. But as things stand, that's my best recommendation for you with MST as-is.