Why don't I get all the same props & methods that the

umb-debug

element has, specifically

UMB_WORKSPACE_CONTEXT

https://cdn.discordapp.com/attachments/882984798719729704/1266051470072086631/image.png?ex=66a3bdd0&is=66a26c50&hm=4f46f66eef421047119140fca7f600e60442b3464ca58bd129e33ea11f6e6bc6&

The workspace context that you see with umb-debug is the actual context instance. Your vscode only has the typings of the generic one, since that is the one you are consuming. The one in your umb-debug window looks like the

UMB_DOCUMENT_WORKSPACE_CONTEXT

which, if you consumed that, you could get IntelliSense for

Yeh figured that out eventually

It's a bit cheeky, but you can typecast the context to any to get access to the instance rather than the interface. Do it, but don't tell anyone you did it.

No I gonna get a massive banner that says Nath said I should 😛

But that is the token (UmbWorkspaceContext). It's because it is generic, so we want you to be able to consume that to "figure out" where you are. You are supposed to typecast it when you have that figured out, or if you know that you are ever only going to display your view for Documents, you can consume the document context directly.

Yeh just a bit confusing umb debug says workspacecontext with all these interesting props & methods then you go use it and find out it has hardly anything. It was only just by fluke I stumbled across the document workspace one. So if umb debug could say which prop & methods are from the generic and which are from the other would be useful for discoverability. Half of the battle learning this stuff is knowing what stuff is where.