feat: enhance prefer-enabled-disabled rule to support the aria-disabled attr

[gnapse]

In light of toBeEnabled and toBeDisabled being enhanced with support for the aria-disabled attribute (testing-library/jest-dom#146) I wanted to go ahead and extend the corresponding eslint rule to detect that attribute as well.

Note: This should not be merged yet, until that change in jest-dom is released, but I was so excited about this eslint plugin and also wanted to make my first contribution ever to a eslint plugin, that I went ahead and did it. I thought it'd take more time but this is very nicely done and was easy to jump in. Still, I'm not sure I'm doing it all right, so let me know.

[benmonro]

sweet, LGTM. just let me know when I can merge

[benmonro]

[benmonro]

@gnapse any update on this? I'd love to merge.

[gnapse]

Thanks for the follow up, as I had forgotten about this.

I recommend closing this. You can check out the discussion in the linked issue in jest-dom that these two are really semantically very different (disabled vs aria-disabled) and it's not advisable to have the both covered under the same matcher.

Feel free to chime in over there if you have some take on all this, or otherwise I'd leave it to you to close this if you agree this should not go through.

[benmonro]

ok closing. feel free to add a rule for toBeAriaDisabled() if that ever gets implemented, would love that.