-
Notifications
You must be signed in to change notification settings - Fork 783
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
Incorrect typings for axe.RunOnly
#972
Comments
yep, it should always be an |
PR - #973 |
Shouldn't the issue stay open until the PR is merged? |
jeeyyy
added a commit
that referenced
this issue
Jun 26, 2018
* fix: update type alias to enum for better typing support. * fix: update type/ inteface names to follow TitleCase. * fix: runOnly interface issue #972 * fix: revert to type over enum, to avoid breaking change/ major release.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The TS definitions for
axe.RunOnly
are incorrect. As suggested by axe-core.org, therunOnly
option should have a propertyvalues
which is an Array of rule IDs. However, in the TS definition,RunOnly
is either an Array ofTagValue
s or aRunOnlyObject
(which has propertiesinclude
andexclude
, making it look like it belongs toElementContext
, notRunOnly
).It looks like these definitions are built by hand, so if you're all on-board, I'd be happy to fix it.
The text was updated successfully, but these errors were encountered: