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
Since 5.7.2, this is what gets generated. Note that ValueIDBase and TBlueprint are generics type arguments used in the transformation that aren't defined in the output file, so the entire types of the meta and options properties effectively resolve to any. It seems that somewhere along the line, TS just gives up resolving:
🔎 Search Terms
unresolved, undefined, declarations
🕗 Version & Regression Information
In a project, I have a relatively complex set of generic types to be able to declare some values that get expanded and merged with defaults at runtime, while exposing that behavior in the type system. This seems to be complex enough that the semantic highlighting in VSCode regularly breaks in that file: https://github.com/zwave-js/zwave-js/blob/133172125d4148ea6e9e92a059b4325862ff6dd7/packages/cc/src/lib/Values.ts
Until TS 5.6.3, this code
would result in a type definition like this:
Since 5.7.2, this is what gets generated. Note that
ValueIDBase
andTBlueprint
are generics type arguments used in the transformation that aren't defined in the output file, so the entire types of themeta
andoptions
properties effectively resolve toany
. It seems that somewhere along the line, TS just gives up resolving:⏯ Playground Link
No response
💻 Code
No response
🙁 Actual behavior
see above
🙂 Expected behavior
see above
Additional information about the issue
I found another issue that might be related, but I'm not familiar enough with the details to know:
#60864
The text was updated successfully, but these errors were encountered: