-
Notifications
You must be signed in to change notification settings - Fork 126
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
Provide a means of filtering errors #34
Comments
Here's the approach I came up with: On Wed, May 20, 2015 at 11:30 AM, Asa Ayers notifications@github.com
|
Sorry, I didn't notice who made the issue and I replied without reading the other notifications :( Great job finding a solution! I looked at the code a bit and it sounds great. Much better than what I came up with :) |
Add a means of filtering failures on a per-component basis (fixes #34…
If you use react-a11y on an existing project, you'll likely be overwhelmed by the number of accessibility errors. It'd be useful to have a means of filtering errors by component name, so developers can easily focus on addressing failures on a per-component basis.
The text was updated successfully, but these errors were encountered: