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.

Sign up for GitHub

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

Jump to bottom

Correct 'recommended' vs 'strict' table #752

Closed
wants to merge 1 commit into from
Closed

Correct 'recommended' vs 'strict' table #752

wants to merge 1 commit into from

Commits on Oct 9, 2020

  1. Correct 'recommended' vs 'strict' table 

    Looking at [this line](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/v6.3.1/src/index.js#L268), I can see that in "recommended" mode, "label-has-for" is set to "off." However, in "strict" mode, it is set to "error."

Although, maybe it should be set to "off" in both cases as it's a deprecated rule?
    @danny-andrews
    danny-andrews committed Oct 9, 2020
    Configuration menu
    Copy the full SHA
    a7a3b1c View commit details
    Browse the repository at this point in the history