Open lukethacoder opened 1 year ago
Can yu clarify the issue? This CEM output looks correct to me.
I'm also curious if this is possible. In my case, Im expecting NumberLike
to resolve to "'foo' | 'bar'"
given its defined as export type NumberLike = 'foo' | 'bar';
See return type:
"declarations": [
{
"kind": "class",
"description": "A number, or a string containing a number.",
"name": "MyElement",
"members": [
{
"kind": "method",
"name": "setMagicNumber",
"parameters": [
{
"name": "x",
"description": "The magic number.",
"type": {
"text": "(number|string)"
}
}
],
"description": "Set the magic number (using a local @typedef annotation).",
"return": {
"type": {
"text": "'foo' | 'bar'"
}
}
}
]
}
]
Checklist
--dev
flag to get more information?Playground Reproduction
Expected behavior
Attempting to resolve external
@typedef
definitions.Output
Hoping that
NumberLikeExternal
andNumberLike
could be resolved to show the actual types, not just the string text of them.