-
Notifications
You must be signed in to change notification settings - Fork 364
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: Initial cSpell setup #841
Conversation
4eae790
to
44cc71e
Compare
Green now. The spelling fixes could be pulled into separate PRs if this doesn't land |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great, @nschonni. Hopefully we can get this merged soon.
@mcking65, this currently won't check spelling on the root aria-practices.html
(soon to be index.html
). I assume it should check spelling there, but thought I'd check with you first.
@nschonni, could you also add an entry to the Travis tests for this that's allowed to fail? It's the kind of feedback that will be useful but shouldn't be blocking.
be031c3
to
de579a0
Compare
Last request: could you resolve the new Travis conflict and add Thanks for all your work on this, @nschonni! |
9926bee
to
49e504e
Compare
eb4fb30
to
d1258cc
Compare
LGTM! Thanks for sticking with this. |
Rebased now that the spellcheck fixes PR landed separately |
2867cb7
to
c0f739b
Compare
Rebased, but didn't fix the new spelling issues that are flagged |
c0f739b
to
a896814
Compare
Remaining spelling fixes split out to #1223 |
c7d6b12
to
c03a2f9
Compare
- All the workds in the settings.json are already in the dictionary - Extension will be "recommended" when opening the workspace in VS Code
d962ec7
to
69d2272
Compare
I've added more words to ignore and rebased on latest master to resolve conflicts with |
I documented this in https://github.com/w3c/aria-practices/wiki/APG-Infrastructure#cspell |
Is this dependent on anything/what needs to be done before this can be merged? |
I think we are good to go. I am curious to see how much it helps us. Our project may not be the best fit for this particular package. @nschonni, I really appreciate all your support here!! |
Infrastructure: Add cSpell to the build process (pull #841) * build: Initial cSpell setup * chore: Add Spelling to CI build * chore: Add cSpell VS Code extension suggestion * Extension will be "recommended" when opening the workspace in VS Code * Add ignored words Co-authored-by: Simon Pieters <[email protected]> Co-authored-by: Zoë Bijl <[email protected]> Co-authored-by: Matt King <[email protected]>
* build: Initial cSpell setup * chore: Add Spelling to CI build * chore: Add cSpell VS Code extension suggestion * Extension will be "recommended" when opening the workspace in VS Code * Add ignored words Co-authored-by: Simon Pieters <[email protected]> Co-authored-by: Zoë Bijl <[email protected]> Co-authored-by: Matt King <[email protected]>
Not all words have been excluded yet, but I figure I'd show the approach before going through everything.
Preview | Diff