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
When using vue-component-meta to analyze component props that utilize namespaced types the library drops the namespace and returns only the base type name.
I would expect the getComponentMeta('').props to return a type Namespace.Data for this particular property, however the returned type is only Data (all the namespaces are dropped).
I found out that this behaviour can be fixed by changing the type generation function from typeChecker.typeToString(subtype) to typeChecker.typeToString(subtype, undefined, ts.TypeFormatFlags.UseFullyQualifiedType).
I am not sure if dropping the namespaces is a feature of the library, but I definitely dont find this behaviour helpful. Can I somehow achieve the same behaviour by extending my repository source code (changing something in tsconfig etc.)? Should I raise a issue for this? Thanks
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When using vue-component-meta to analyze component props that utilize namespaced types the library drops the namespace and returns only the base type name.
When I define component types like this:
I would expect the
getComponentMeta('').propsto return a typeNamespace.Datafor this particular property, however the returned type is onlyData(all the namespaces are dropped).I found out that this behaviour can be fixed by changing the type generation function from
typeChecker.typeToString(subtype)totypeChecker.typeToString(subtype, undefined, ts.TypeFormatFlags.UseFullyQualifiedType).I am not sure if dropping the namespaces is a feature of the library, but I definitely dont find this behaviour helpful. Can I somehow achieve the same behaviour by extending my repository source code (changing something in tsconfig etc.)? Should I raise a issue for this? Thanks
Beta Was this translation helpful? Give feedback.
All reactions