fix: support cspell.config.js and remove support for cspell.js
#895
Conversation
This file contains 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
No need to have support for package.json yet.
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.
Supported list of configuration files:
Primary configuration file names:
Alternate locations: might be removed in the future.
Note: Missing from the list is
cspell.jsandpackage.json.cspell.js- causes issues withnpx cspellwhen run from the same directory as acspell.jsconfig file. See Issues with usingcspell.jsconfig files. #891package.json- No need to add support for acspellsection of apackage.jsonfile until there is a compelling reason to add it there.