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).
What does the proposed solution look like?
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. I would be glad if I can turn this setting on in MetaCheckerOptions.
The text was updated successfully, but these errors were encountered:
Besides this issue, I also encounter a problem with type truncation. When a props is defined as a large union the type is truncated to ... XX more ..., which is not a valid type. I found out that using ts.TypeFormatFlags.NoTruncation solve this particular problem.
What problem does this feature solve?
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 props like this:
I would expect the
getComponentMeta('').props
to return a typeNamespace.Data
for this particular property, however the returned type is onlyData
(all the namespaces are dropped).What does the proposed solution look like?
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. I would be glad if I can turn this setting on in MetaCheckerOptions.
The text was updated successfully, but these errors were encountered: