-
-
Notifications
You must be signed in to change notification settings - Fork 393
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
Linter for well-known noninclusive words #3059
Comments
@alice linked to this on twitter: I think it would be awesome to have this as a linter, along with recommendations for alternatives. @saschanaz, something you'd wanna build? |
Specberus has this already: https://github.com/w3c/specberus/blob/main/lib/rules/structure/neutral.js Might be better to delegate that to spec-prod instead of ReSpec? w3c/spec-prod#3 |
Good idea 😃 |
I guess it depends if we can get echidna checks running earlier... it's nice getting those kinds of warnings early in the spec development process (i.e., as someone is editing locally, instead of pre-publication). |
Closing as we now support pub rules on spec-prod. |
Is your feature request related to a problem? Please describe.
Some specifications still have noninclusive words including blacklists: https://w3c.github.io/webcrypto/KeyDiscovery.html
A linter will be helpful to detect and remove them.
Describe the solution you'd like
Warn wherever such words exist with a way to suppress it
The text was updated successfully, but these errors were encountered: