fix(vscode-webui): refine i18next ESLint rules to reduce false positives #642
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
This PR refines the i18next ESLint configuration for the vscode-webui package to significantly reduce false positives while maintaining effective internationalization coverage:
jsx-text-onlytojsx-onlyto enable targeted attribute checkingjsx-attributeswhitelist to only check user-facing attributes (title,alt,placeholder,label)These changes focus the linting on actual user-facing text that needs translation, while ignoring technical attributes like
className,variant,size, and developer-oriented function arguments.Test plan
i18next/no-literal-stringplugin's documented options🤖 Generated with Pochi