bug: fix summary being treated as non-interactive#985
bug: fix summary being treated as non-interactive#985khiga8 wants to merge 2 commits intojsx-eslint:mainfrom
Conversation
|
I am going to test bumping If bumping this package should be done with more care/breaks things, then I may instead suggest a hard-coded update to |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #985 +/- ##
==========================================
- Coverage 99.03% 99.02% -0.01%
==========================================
Files 107 105 -2
Lines 1651 1638 -13
Branches 581 581
==========================================
- Hits 1635 1622 -13
Misses 16 16 ☔ View full report in Codecov by Sentry. |
|
Good job. Was hoping a fix was one the way for this issue :) |
|
rebased, but it's failing. |
|
@khiga8 we're stuck on an older version of aria-query and axobject-query, which don't have "summary" in the right place, so i think it is still needed. |
|
@ljharb I'm the blocker here. Would you like permission to publish updates for aria-query and axobject-query? I'd like to remove myself from the dependency chain here so folks are unblocked. I'm flat out with work-work and family lately and I don't have the bandwidth to jump in here. |
|
@jessebeach i'd be more than happy to help maintain those projects! I'd still want you to weigh in on the dequal breaking change stuff tho, which is the blocker for us upgrading. |
You're a maintainer now. That's one hurdle =D |
|
@jessebeach thanks! do i need npm ownership as well? |
I invited you to both NPM projects. That's 2 hurdles =D |
89301a8 to
67210fc
Compare
|
I've rebased this onto main, which has unpinned axobject-query, but aria-query still needs a release for us to be able to unpin it, and presumably at that point this PR will pass tests. |
Fixes: #656
This ensures that
summaryis treated as an interactive element so it doesn't raise a false positive with theno-static-element-interactionslint rule.