Skip to content

Fix autocomplete-valid-test #665

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

Closed
wants to merge 1 commit into from

Conversation

matijs
Copy link
Contributor

@matijs matijs commented Feb 23, 2020

data was never passed and .fail is not a function.

@WilcoFiers ._audit looks like it's axe-core internal and it's the only reason axe-core is used in eslint-plugin-jsx-a11y. Are there plans to make this part of the public axe-core API?

`data` was never passed and `.fail` is not a function.
@matijs
Copy link
Contributor Author

matijs commented Feb 23, 2020

Cloning the repo and running npm install results in axe-core v3.5.1 being installed. Tests fail using this version.

Fixing the tests makes them pass locally but then they fail in CI (Does Travis use a cached version of node_modules somehow?).

Experimenting with manually downgrading axe-core has these results:

branch axe-core result
master v3.5.1 fail
master v3.4.2 fail
master v3.4.1 pass
matijs:fix/autocomplete-valid-test v3.5.1 pass
matijs:fix/autocomplete-valid-test v3.4.2 pass
matijs:fix/autocomplete-valid-test v3.4.1 fail

It looks like this change that ended up in axe-core v.3.4.2 is responsible for the tests failing, but since _audit suggests it's internal… I'm not sure what to do.

@matijs
Copy link
Contributor Author

matijs commented Feb 23, 2020

Looked into why there was no lockfile and found this PR. @ljharb I was wondering if you still feel the same way.

@ljharb
Copy link
Member

ljharb commented Feb 23, 2020

Always and forever, only apps should have lockfiles.

@ljharb
Copy link
Member

ljharb commented Feb 23, 2020

Observable is public, so this looks like a breaking change in a patch version of axe-core. We can peg the version in package.json to get tests passing again.

matijs referenced this pull request in matijs/eslint-plugin-jsx-a11y Feb 24, 2020
Pin axe-core to v3.4.1 which is the latest version in which tests for
the 'autocomplete-valid' rule pass.

See [this
PR](https://github.com/evcohen/eslint-plugin-jsx-a11y/pull/665) for more
information and small discussion.
@matijs matijs mentioned this pull request Feb 24, 2020
@matijs
Copy link
Contributor Author

matijs commented Feb 24, 2020

Closed in favour of #666

@matijs matijs closed this Feb 24, 2020
@matijs matijs deleted the fix/autocomplete-valid-test branch February 24, 2020 08:24
matijs referenced this pull request in matijs/eslint-plugin-jsx-a11y Feb 24, 2020
Pin axe-core to v3.4.1 which is the latest version in which tests for
the 'autocomplete-valid' rule pass.

See [this
PR](https://github.com/evcohen/eslint-plugin-jsx-a11y/pull/665) for more
information and small discussion.
ljharb pushed a commit to matijs/eslint-plugin-jsx-a11y that referenced this pull request Feb 26, 2020
Pin axe-core to v3.4.1 which is the latest version in which tests for the 'autocomplete-valid' rule pass.

See jsx-eslint#665 and dequelabs/axe-core#2060 for more information and small discussion.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants