-
Notifications
You must be signed in to change notification settings - Fork 4.7k
feat: documentation linting #1745
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
Conversation
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.
Awesome work! 🎉
(This is not 100% related, by we don't have a CONTRIBUTING.md
guide in the repo, which I guess should be the next task after #1745)
@sarahdayan how about Chinese and Russian languages? Are they supported? |
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.
Awesome work!
Hey @sarahdayan, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚 |
Unfortunately they're not. There are some rules for Japanese out there, but if we want to support Chinese and Russian we'll have to create new rules. |
Summary
This PR adds content linting to the documentation of VuePress, using textlint.
Some rules (the more subjective ones) are set with a warning severity, meaning they wouldn't make a CI fail. It also leaves the possibility of progressively fixing things.
The PR is quite large because it also embarks a first run at fixing issues that were revealed by textlint.
What kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
Other information:
Content linting was added as a pre-commit hook. I changed the way the other pre-commit hook was wired so the whole thing works properly across the monorepo.
❓Question: for now, the linting precommit hooks are split into two:
docs/
(the one created in this PR)They're triggered by running the global precommit first, then the local ones with
lerna run
.Ideally, it's better to have a command per repo. Do we think it's worth it?