You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this example, the type X resolved to any instead of:
// an opaque type of x"x"&{__type: "x";}
And this shouldn't work but does autocomplete on the import. It is incorrect because Concat can only be accessed from tb.T or tb.Tuple. So it seems like there is a confusion between namespaces and modules with the playground.
I think it is important to note that types which are exposed from top-level (not modules in modules) do work. But not when you have types -> in modules -> in modules. Something that is of the form:
ModuleA: # A Module that exports
- SubModuleA1 # Submodules that export
- Types # Multiple types
- SubModuleA2
- TypesModuleB:
- SubModuleB1
- Types
- SubModuleB2
- Typesexport All: # All parents exported
- ModuleA
- ModuleB
The text was updated successfully, but these errors were encountered:
Thanks - Yeah, I think this could only be fixed by moving to a completely virtual fs based ATA - which is something Monaco-typescript explicitly doesn't want to support.
Not sure how we're going to bridge that gap in the long run yet.
In this example, the type
X
resolved toany
instead of:And this shouldn't work but does autocomplete on the import. It is incorrect because
Concat
can only be accessed fromtb.T
ortb.Tuple
. So it seems like there is a confusion between namespaces and modules with the playground.I think it is important to note that types which are exposed from top-level (not modules in modules) do work. But not when you have types -> in modules -> in modules. Something that is of the form:
The text was updated successfully, but these errors were encountered: