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: add option to set severity levels automatically based on Rule and Categoy #651

Merged
merged 1 commit into from
Mar 2, 2024

Conversation

kanutron
Copy link
Contributor

This change allows the user to let the severity levels be determined by the Extension as follows:

  • All spelling mistakes are underlined in red (Error)
  • All punctuation, grammar or typography mistakes in yellow (Warning)
  • Any other mistake will be set as the defined Severity Level, which can be set as Information as recommended

The configuration option is a simple boolean that enables this feature. By default, is disabled, so users will notice no change unless explicitly activated.

A potential improvement could be to sophisticate the options, allowing the user to choose which rules or categories are forced to a specific severity level, similar to allowing them to ignore some rules or categories.

@davidlday davidlday changed the title Added an option to set severity levels automatically based on Rule and Categoy feat: add option to set severity levels automatically based on Rule and Categoy Feb 26, 2024
@davidlday
Copy link
Owner

@kanutron - thanks for the contribution! I'm getting caught up on dependency updates, but hope to get this merged in today or tomorrow.

@kanutron
Copy link
Contributor Author

Awesome. Let me know if I can help on anything.

…pelling) and Category (grammar, punctuation, typography).
@davidlday
Copy link
Owner

@kanutron - apologies for taking longer than expected! Wrapping up now.

@davidlday davidlday self-requested a review March 2, 2024 16:27
@davidlday davidlday merged commit 3c515f4 into davidlday:master Mar 2, 2024
8 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