v15.1.0 #1611
Merged
v15.1.0 #1611
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's Changed
Key Features
This release includes two major improvements to textlint's severity system and configuration handling:
1. New
infoSeverity Level (PR #1610)We've implemented proper support for the
infoseverity level, which provides more flexible linting for informational messages that are less critical than warnings.Background: Previously,
infohad the same value asnone(0), causing confusion. Nowinfohas its own distinct value (3) and is properly supported across all formatters.Use Case: This is particularly useful for AI-assisted writing rules, such as those in textlint-ja/textlint-rule-preset-ai-writing, which provides LLM-oriented rules for guidelines. These rules can be somewhat broad and may produce false positives if used as errors, but when reported as
info, they provide more flexible feedback for AI agents and human writers.Severity Levels:
none: 0- Disabledwarning: 1- Warning (yellow)error: 2- Error (red)info: 3- Informational (green)Example Usage:
{ "rules": { "my-rule": { "severity": "info" // Now properly displays as green "info" } } }2. Fixed Preset Severity Preservation (PR #1607)
Fixed an issue where preset-defined severity settings were lost when users provided partial rule configuration in their
.textlintrcfile.Problem: When using a preset that defined severity levels for rules, those settings were completely lost if users added any custom options for those rules.
Solution: Implemented a clear priority system where user configuration completely overrides preset configuration when provided (no merging), making behavior predictable and consistent.
Related Issues: Fixes #1608, #1606
Features
infoseverity level by @azu in feat: implementinfoseverity level #1610Bug Fixes
trueconfig by @azu in fix: preserve preset severity settings when user providestrueconfig #1607Documentation
Testing
truecase by @azu in test(config-loader): add user config istruecase #1609CI
Dependency Updates
Other Changes
New Contributors
Full Changelog: v15.0.1...v15.1.0