Skip to content

add severity to "unknown section" diagnostic#32

Open
senekor wants to merge 2 commits intoJFryy:mainfrom
senekor:senekor/kxsxxkxrosuu
Open

add severity to "unknown section" diagnostic#32
senekor wants to merge 2 commits intoJFryy:mainfrom
senekor:senekor/kxsxxkxrosuu

Conversation

@senekor
Copy link
Copy Markdown
Contributor

@senekor senekor commented Apr 11, 2026

What does this PR do?

It adds the severity level "warning" to the "unknown section" diagnostic.

Fixes #31.

How did you test this?

Open a file with the content "[A]" in Helix, to trigger the diagnostic. Then open the diagnostic picker with "space d" to confirm the "severity" column is non-empty. In many themes, there is also a visual difference (e.g. kanagawa).

@senekor senekor mentioned this pull request Apr 11, 2026
@senekor senekor force-pushed the senekor/kxsxxkxrosuu branch from 2112928 to cec6a21 Compare April 11, 2026 20:51
@senekor
Copy link
Copy Markdown
Contributor Author

senekor commented Apr 11, 2026

Oh, I wanted to target the branch of PR #33, so this diff is kept clean. But I can't, since the PR is from a fork. Only the diff of commit cec6a21 really belongs here. If PR #33 is merged, the diff here should become clean.

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.

Not all diagnostics have a severity

1 participant