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
When comparing VS Code behaviour with Web Storm, type aliases are expanded, so when you have a type of like:
type TypeAlias = string;
And then use it:
const TestWithAlias: Record<TypeAlias, string> = {};
VS Code will expand the type where Web Storm will not.
It would be nice to have an option to not expand type aliases.
Here are screenshot examples of the behaviors of both IDEs, VS Code first, Web Storm second.
And here is the code used: https://www.typescriptlang.org/play/?#code/C4TwDgpgBAKuEEEA2BLAhgZygXih4ATigHYDmA3AFCWiRQCyaYA6isABZyTLoYDSEEDigAlCAGMA9gQAmAHi6JUmADR5CJUgD4qlKcXxQA7gUlkBIRQC4GTVh0U9MF4QG8AvuSA
The text was updated successfully, but these errors were encountered:
duplicate of or at least strongly related to #45954
Sorry, something went wrong.
@jcalz yes, it seems like this is a duplicate. I'll close this issue now.
No branches or pull requests
When comparing VS Code behaviour with Web Storm, type aliases are expanded, so when you have a type of like:
And then use it:
VS Code will expand the type where Web Storm will not.
It would be nice to have an option to not expand type aliases.
Here are screenshot examples of the behaviors of both IDEs, VS Code first, Web Storm second.
And here is the code used: https://www.typescriptlang.org/play/?#code/C4TwDgpgBAKuEEEA2BLAhgZygXih4ATigHYDmA3AFCWiRQCyaYA6isABZyTLoYDSEEDigAlCAGMA9gQAmAHi6JUmADR5CJUgD4qlKcXxQA7gUlkBIRQC4GTVh0U9MF4QG8AvuSA
The text was updated successfully, but these errors were encountered: