Open
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.
💻 变更类型 | Change Type
🔀 变更说明 | Description of Change
During the
git commitprocess,lint-stagedis triggered by a huskypre-commithook to run ESLint.Because
302.AIis not a valid JavaScript identifier, theeslint-plugin-unused-importsplugin encounters an un-parsable syntax structure. This causes an internal error within the plugin, which aborts thepre-commithook and prevents the commit from completing.To resolve this parsing error within the ESLint plugin, this PR introduces the following changes:
302.AItoAI302, which is a standard, valid JavaScript identifier.These changes ensure that the
eslint-plugin-unused-importsplugin can parse the code correctly, allowing the pre-commit hook to execute successfully.📝 补充信息 | Additional Information