Open gf3 opened 8 years ago
Hmm, this would actually be hard to d without also keeping information on exactly why the rule failed (eg. what values do the props have that cause the rule to fail), or we might miss some errors. This would be a big refactor (every test would need to be rewritten), so not a real priority as of yet.
From the screenshot it seems that you are re-rendering the same components over and over again, perhaps you should consider trying to reduce re-renders. Of course fixing the error or disabling the rule would be a quick way to alleviate this problem.
There is a bit of a "feature" that could be considered here. The amount of noise and pain it causes when you don't meet a11y standards really motivates you to fix the issue. 😉
When a component is re-rendered the warnings for any child components are displayed again. This can be quite noisy (e.g. when a component is re-rendered on keyboard input). Perhaps warnings should be cached by warning type + DOM node and only displayed once?