-
Notifications
You must be signed in to change notification settings - Fork 74
Console: enhanced warning reporting #681
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
base: master
Are you sure you want to change the base?
Conversation
Also we could use workflow annotations, but it would cause extra warnings. This is because the "SelfCheck" step runs three times, once for each operating system and we may encounter additional and repetitive warnings. |
f8e42d8
to
0004f69
Compare
I don't understand this claim. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rebase, please
Improved warning reporting to display line number and column in the format: `fileName.fs(lineNumber, column)`. This feature is particularly useful in environments like VSCode, which highlights these locations and makes them clickable. When clicked, VSCode will open the corresponding file at the exact line and position of the cursor. This functionality allows developers to quickly navigate to the source of the issue, significantly speeding up the debugging process.
I rebased, and here is what the new warning message looks like:
|
But at the beginning of the output, there is a line Could you compare your new output to the output with |
Improved warning reporting to display line number and column
in the format:
fileName.fs(lineNumber, column)
.This feature is particularly useful in environments like
VSCode, which highlights these locations and makes them
clickable. When clicked, VSCode will open the corresponding
file at the exact line and position of the cursor.
This functionality allows developers to quickly navigate to the
source of the issue, significantly speeding up the
debugging process.