Fix mismatched refs lint suppression scope in useTabular
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
Research direction
Open packages/graph-explorer/src/components/Tabular/useTabular.ts around lines 427 and 435, then compare the rule names with the react-compiler configuration in .oxlintrc.json at lines 99 and 120. Update the mismatched re-enable directive and run the relevant Oxlint check to confirm the suppression ends after the react-table options object.
Written by the indexing model from the issue text.
Description
Description
packages/graph-explorer/src/components/Tabular/useTabular.ts:427 opens a block disable for react-compiler/refs, but the matching re-enable at :435 names react-hooks/refs — a namespace that is not loaded (the jsPlugin is named react-compiler in .oxlintrc.json:99, and the rule is enabled at :120). Oxlint pairs disable/enable directives by rule name, so the re-enable never matches and the disable leaks to the end of the file. react-compiler/refs therefore stays off for everything after the react-table options object.
Proposed change
Change the re-enable at :435 to /* oxlint-enable react-compiler/refs */, scoping the suppression to the options object. There are no .current reads after :435, so no new violations appear.
Affected
packages/graph-explorer/src/components/Tabular/useTabular.ts:427,435
[!IMPORTANT]
If you are interested in working on this issue, please leave a comment.
[!TIP]
Please use a 👍 reaction to provide a +1/vote. This helps the community and maintainers prioritize this request.
[!NOTE]
A maintainer will need to set this issue's type toTask; external contributors cannot set issue types.
- Dominant language
- TypeScript
- Stars
- 481
- Forks
- 110
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aws/graph-explorer
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aws/graph-explorer#2203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
aws/graph-explorer#2196 · 2 comments ·
-
help wanted needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
aws/graph-explorer#2060 ·
-
help wanted reliability usability
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
aws/graph-explorer#1977 · 2 comments ·
-
documentation usability
Difficulty 2/5 1-2 days Newbie friendliness 68/100
aws/graph-explorer#1719 ·
All issues in aws/graph-explorer
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100