fix: resolve format-message lint warnings for dynamic message patterns#91
Merged
takaokouji merged 1 commit intodevelopfrom Jan 16, 2026
Merged
Conversation
- Add .format-message-lint.json to configure format-message lint rules - Disable literal-pattern and literal-locale rules (severity 0) as these are false positives for the maybeFormatMessage function which is designed to handle dynamic message objects from extensions - Maintain all other default lint rules for message validation - Update package.json lint script to use custom rules configuration Fixes smalruby/smalruby3-develop#21 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
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.
Summary
format-message lintcommandImplementation Details
The
maybeFormatMessagefunction is designed to handle dynamic message objects from extensions, which triggersliteral-patternandliteral-localewarnings. These are false positives since the function intentionally accepts non-literal patterns.Solution:
.format-message-lint.jsonwith custom rules configurationliteral-patternandliteral-localerules (severity 0)package.jsonlint script to use-e customrules -c .format-message-lint.jsonTest Coverage
npm run lint # Result: 0 errors, 0 warningsFiles Changed
.format-message-lint.jsonpackage.jsonFixes smalruby/smalruby3-develop#21
🤖 Generated with Claude Code