We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
types misplaced not displayed
I have this code:
export const BODY_TYPES = { DYNAMIC: 1, STATIC: 2, KINEMATIC: 4, } as const export type BodyType = typeof BODY_TYPES[keyof typeof BODY_TYPES] export class Body { /** * One of: `Body.DYNAMIC`, `Body.STATIC` and `Body.KINEMATIC`. */ type: BodyType // ... constructor( options: { /** * One of: `Body.DYNAMIC`, `Body.STATIC` and `Body.KINEMATIC`. */ type?: BodyType // ... } = {} ) { }
And the options.type is not showing the BodyType, but instead its literal value (happens from v0.20.6, possibly related to #1528).
options.type
BodyType
v0.20.6
While the class property, is showing totally a different type!! (happens from v0.20.13)
v0.20.13
For context, the type RayMode is in totally another part of the application and corresponds to this:
RayMode
export const RAY_MODES = { CLOSEST: 1, ANY: 2, ALL: 4, } as const export type RayMode = typeof RAY_MODES[keyof typeof RAY_MODES]
This should be the correct behaviour as it is with v0.20.5:
v0.20.5
I can link the repo where this happens if needed
The text was updated successfully, but these errors were encountered:
What TypeScript version are you using?
Sorry, something went wrong.
4.0.5, but I'll try upgrading it and see if the issue persists!
Updating typescript completely solves this issue, thanks!
No branches or pull requests
Search terms
types misplaced not displayed
Actual Behavior
I have this code:
And the
options.type
is not showing theBodyType
, but instead its literal value (happens fromv0.20.6
, possibly related to #1528).While the class property, is showing totally a different type!! (happens from
v0.20.13
)For context, the type
RayMode
is in totally another part of the application and corresponds to this:Expected Behavior
This should be the correct behaviour as it is with
v0.20.5
:Steps to reproduce the bug
I can link the repo where this happens if needed
Environment
The text was updated successfully, but these errors were encountered: