microsoft / TypeScript Public
New issue
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
Improve positioning of compiler error messaging info #47126
base: main
Are you sure you want to change the base?
Conversation
|
@typescript-bot pack this |
|
Hey @orta, I've packed this into an installable tgz. You can install it for testing by referencing it in your and then running There is also a playground for this build and an npm module you can use via |
|
@typescript-bot pack this |
|
Hey @orta, I've packed this into an installable tgz. You can install it for testing by referencing it in your and then running There is also a playground for this build and an npm module you can use via |
|
@typescript-bot pack this |
|
Hey @orta, I've packed this into an installable tgz. You can install it for testing by referencing it in your and then running There is also a playground for this build and an npm module you can use via |
Fixes #45717.
This PR improves the formatting of compiler error messages for better legibility as described in the referenced issue.
Two concerns that are worth noting with this PR;
Moving the error next to the file means that the error code doesn't show in, for example, the "file not found" error message. Not that it's all that necessary with clear and detailed error messages in that case in particular, but there are most likely others I'm not aware of.
With errors that contain multiple code spans, the message for subsequent locations is moved above the code itself, which means that some error messages might need to be subtly changed. For example, in this comment, the period at the end of the "was also declared" messages is changed to a colon.
The text was updated successfully, but these errors were encountered: