[BUG] React Hook dependency warnings in multiple components

[Sam-61s]

Describe the bug.

Multiple components across the website have ESLint react-hooks/exhaustive-deps warnings. These warnings indicate missing or unnecessary dependencies in React hooks, which can lead to stale closure bugs and unexpected component behavior.

Running npm run lint reveals 8 warnings across 7 component files where useEffect and useMemo hooks don't properly declare their dependencies.

Affected components:

• components/AlgoliaSearch.tsx (line 318)
• components/campaigns/AnnouncementHero.tsx (line 24)
• components/dashboard/table/Filters.tsx (line 42)
• components/navigation/DocsNav.tsx (line 79)
• components/navigation/Filter.tsx (lines 35, 39)
• components/tools/ToolsCard.tsx (line 35)
• components/tools/ToolsDashboard.tsx (line 166)

Expected behavior

All React hooks should properly declare their dependencies in their dependency arrays.

Expected output:
npm run lint
✔ No ESLint warnings

Screenshots

❌ The Problem:

✅ The Solution:

How to Reproduce

1. Clone the repository
2. npm install
3. npm run lint
4. Observe React Hook dependency warnings

Current output:
./components/AlgoliaSearch.tsx
318:6 Warning: React Hook useEffect has missing dependencies...

./components/campaigns/AnnouncementHero.tsx
24:106 Warning: React Hook useMemo has an unnecessary dependency...

./components/dashboard/table/Filters.tsx
42:6 Warning: React Hook useEffect has a missing dependency...

./components/navigation/DocsNav.tsx
79:6 Warning: React Hook useEffect has a missing dependency...

./components/navigation/Filter.tsx
35:6 Warning: React Hook useEffect has missing dependencies...
39:6 Warning: React Hook useEffect has missing dependencies...

./components/tools/ToolsCard.tsx
35:6 Warning: React Hook useEffect has an unnecessary dependency...

./components/tools/ToolsDashboard.tsx
166:6 Warning: React Hook useEffect has a missing dependency...

🖥️ Device Information [optional]

• Operating System (OS):: Linux (WSL2), Windows, macOS (affects all)
• Browser: N/A (this is a build-time linting issue)
• Browser Version:

👀 Have you checked for similar open issues?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue ?

Yes I am willing to submit a PR!

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[Sam-61s]

Hi @antoniogarrote , I'd like to work on this issue. I have already fixed all the warnings locally and tested the solution. Could you please assign this to me? Thanks!

[dhiraj-143r]

I am working on it

[Sam-61s]

Hi @dhiraj-143r,
Thanks for your work on this!

Just a quick reminder based on AsyncAPI’s contribution guidelines: contributors should wait for the issue to be approved by maintainer before starting work to avoid duplication. I had requested assignment earlier since I already had the fix ready.

please follow the assignment workflow next time. Also, please check the AsyncAPI contribution guidelines here: https://github.com/asyncapi/community/blob/master/CONTRIBUTING.md

I’m currently waiting for maintainer approval on this issue. Thanks for understanding!

[dhiraj-143r]

my bad