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

Feat: Configure diagnostic severity per linter #306

Open
ficcdaf opened this issue Dec 6, 2024 · 3 comments · May be fixed by #312
Open

Feat: Configure diagnostic severity per linter #306

ficcdaf opened this issue Dec 6, 2024 · 3 comments · May be fixed by #312

Comments

@ficcdaf
Copy link

ficcdaf commented Dec 6, 2024

Currently, the diagnosticSeverity configuration option applies globally to all of Harper's output. However, it would be nice to have an option to configure a different severity for each linter. For example, I would like to set spell_check and sentence_capitalization to the error severity, while some other things like spaces and linking_verbs would make more sense as warning or info. For reference, ltex-ls implements this feature.

grantlemons added a commit to grantlemons/harper that referenced this issue Dec 11, 2024
grantlemons added a commit to grantlemons/harper that referenced this issue Dec 11, 2024
grantlemons added a commit to grantlemons/harper that referenced this issue Dec 12, 2024
grantlemons added a commit to grantlemons/harper that referenced this issue Dec 12, 2024
grantlemons added a commit to grantlemons/harper that referenced this issue Dec 12, 2024
grantlemons added a commit to grantlemons/harper that referenced this issue Dec 12, 2024
@elijah-potter elijah-potter linked a pull request Dec 30, 2024 that will close this issue
@elijah-potter
Copy link
Collaborator

elijah-potter commented Dec 30, 2024

Hey @ficcdaf,

I like this idea. I don't imagine this would be difficult to implement. It is somewhat lower priority, so it might be a bit before I can get to it. It looks like @grantlemons has taken it up. He might be able to provide a status on it.

Thanks for raising the issue!

@grantlemons
Copy link
Contributor

Status was that it was supported by harper-ls, but still needed integration with harper-wasm, and the vscode plugin.

I'll need to revisit it to ensure nothing was broken by all the changes to master recently.

@ficcdaf
Copy link
Author

ficcdaf commented Dec 31, 2024

No problem and no rush. Thanks for all your hard work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants