Skip to content
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

Open
wraithgar opened this issue Mar 8, 2023 · 1 comment
Open

a11y office hours notes #652

wraithgar opened this issue Mar 8, 2023 · 1 comment
Assignees

Comments

@wraithgar
Copy link
Member

wraithgar commented Mar 8, 2023

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.

@wraithgar wraithgar self-assigned this Mar 8, 2023
@kendallgassner
Copy link

kendallgassner commented Mar 8, 2023

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
Projects
None yet
Development

No branches or pull requests

3 participants