[BUG]: Duplicate technology filter logic in handleApplyFilters causes redundant code

Open Beginner friendly
#4,894 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
react, typescript
Domain
frontend

Research direction

Open components/tools/Filters.tsx and navigate to handleApplyFilters. Inspect the repeated checkedTechnology filter logic, remove the redundant application, and verify that each filter is applied only once in the function and that the filter UI still behaves as expected.

Written by the indexing model from the issue text.

Description

bug stale
Describe the bug.

In components/tools/Filters.tsx, the handleApplyFilters function applies the technology filter twice.

Expected behavior

Each filter should be applied only once inside handleApplyFilters.

Screenshots
Image
How to Reproduce
  1. Open components/tools/Filters.tsx and navigate to the handleApplyFilters function.
  2. Notice that the checkedTechnology filter logic is applied twice.
🖥️ Device Information [optional]
  • Operating System (OS):
  • Browser:
  • Browser Version:
👀 Have you checked for similar open issues?
  • I checked and didn't find similar issue
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue ?

Yes I am willing to submit a PR!

Dominant language
TypeScript
Stars
717
Forks
1.2k
Avg merge
14h 59m
Merged PRs (30d)
40

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from asyncapi/website

All issues in asyncapi/website

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.