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
Ruby: improve diagnostic messages #12216
Conversation
For now we only report real parse errors and character encoding errors. Warnings about unexpected or missing nodes in the AST are not reported. These are typically side effects of earlier parse errors.
01d0f29
to
c4b0503
Compare
a2be8d8
to
f71c330
Compare
ruby/extractor/src/extractor.rs
Outdated
| .severity(diagnostics::Severity::Error) | ||
| .location(self.path, start_line, start_column, end_line, end_column) | ||
| .text(&error_message) | ||
| .status_page(), | ||
| .message("unknown table type: {}", &[node.kind()]), |
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.
I notice an inconsistency in the capitalization of the message text - is there a convention or style guide to refer to about this?
cffdde3
to
91eba87
Compare
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.
I'm not that confortable in Rust, and I had to read up on what e.g. with_capacity does.
But everything I understand, I approve of ![]()
You are doing more kinds of diagnostics messages than I had expected.
No description provided.