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
custom component settings don't seem to be working? #857
Comments
I had the same problem! Did you find any solution for this? Thank you! |
I have not, really hoping someone picks this up and it turns out to be something simple |
That's because they're not released yet - they were added in #844. Always look at the docs for the version tag you're using, not the ones on main. |
I see now, that it's been merged, any idea on when we could expect the next version that includes this feature? I will probably install it from the git URL to get this as I would really like to start using this now |
You can't install it from git, because there's a build process. There's no timeline for releases, but I am hoping soon. |
Yeah I just looked at that, suppose I could build manually and link it possibly but hopefully the NPM version will see a new build with this feature soon |
I've followed the setup to get custom components to be recognized and for the aria rules to throw but they aren't working
Here is the config I'm working with
All the other rules work so I know that eslint is working here
When I attempt to use the
Box
element from MUI I'm not getting any warnings at all when I for instance have this...But when I change that
Box
to adiv
I get the rule warning that a role needs to be added to interactive elements. Am I missing some kind of config or setup here?The text was updated successfully, but these errors were encountered: