Skip to content
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

Don't offer a code action for a diagnostic with no diagnostic "code" #100

Merged
merged 2 commits into from
Jan 25, 2025

Conversation

mtbentley
Copy link

Per the lsp spec, a diagnostic code, if one exists, should be a number or a string. At least one error message (the help message for missing imports) doesn't include a code, so the parse_line function sets it to "None".

When this happens, don't offer a code action for that diagnostic

#99

mtbentley and others added 2 commits January 2, 2025 23:08
Per the lsp spec, a diagnostic code, if one exists, should be a number
or a string.  At least one error message (the help message for missing
imports) doesn't include a code, so the parse_line function sets it to
"None".

When this happens, don't offer a code action for that diagnostic
@Richardk2n
Copy link
Member

As per the spec, the code is optional and should therefore probably not be included at all if it is not valid.

@Richardk2n Richardk2n merged commit 64e2f89 into python-lsp:master Jan 25, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants