Improve spell checking on local development #4
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
chore: Install CSpell if needed feat: Add VS Code tasks to run CSpell locally
|
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
Adds VS Code tasks and updated the devcontainer to be able to run CSpell spell check locally.
Also adds a local development section to the Contributing docs.
Checklist
Addresses issue #ISSUE_NUMBER (if applicable)
What type of changes does this PR include
Describe the change in more detail
Previously you would need to wait for the CI/CD pipelines to tell you if there was a problem with a spellcheck word. Now you can find out quickly when you build the module.