-
Notifications
You must be signed in to change notification settings - Fork 52
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
a11y office hours notes #652
Labels
Comments
I am so exciting for these linting rules ❤️ ... or output test 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Log output going to stdout does not need to match what's in the logs. It's way too repetitive.
Lot output customization would be helpful (basic templating like
"{index} {level}: {subject}\n{message}"
urls should always be on their own line (good first output linting rule)
Linting is harder because unlike html the source is completely decoupled from the output. There's no source to meaningfully lint. It will have to be output testing. We already have a mock npm object that knows everything it sent to stdout. The teardown (or t.after) for that object is where we can start to do static analysis of cli output.
normal stdout does not need to be considered part of the semver contract (json and parseable still are of course)
markdown and commit messages should not have line length limits.
The text was updated successfully, but these errors were encountered: