Derive maintainers IssuesTab category/language filters from API data instead of hardcoded lists

[Jagadeeshftw]

📌 Description

IssuesTab (src/features/maintainers/components/issues/IssuesTab.tsx) hardcodes its category and language filter options (e.g. 'Blockchain', 'JavaScript'), so filters never reflect the actual labels/languages present in the loaded issues.

💡 Why it matters: Hardcoded filters miss real categories and offer irrelevant ones.

🧩 Requirements and context

• Build the category and language filter option sets from the loaded issue data.
• Keep filters in sync as the issue set changes.
• Show an issues fetch error state (currently only PR fetch errors are surfaced).

Non-functional requirements

• Must be secure, tested, and documented.
• Should be efficient and easy to review.

🛠️ Suggested execution

1. Fork the repo and create a branch

git checkout -b refactor/issuestab-dynamic-filters

2. Implement changes

• Write/modify the relevant source: src/features/maintainers/components/issues/IssuesTab.tsx
• Write comprehensive tests: src/features/maintainers/components/issues/IssuesTab.test.tsx
• Add documentation: inline TSDoc
• Include TSDoc doc comments
• Validate security assumptions: escape derived label text

3. Test and commit

• Run tests:

npm run test

• Cover edge cases: no labels, many labels, issues fetch error
• Include test output and security notes in the PR description.

Example commit message

refactor(issues): derive filters from data + issues error state

✅ Acceptance criteria

• Filters derived from loaded issues
• Filters update with data changes
• Issues fetch error surfaced
• Tests cover dynamic filters + error

🔒 Security notes

Escape label/language strings from external repos.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[ekwe7]

I'd love to take on this issue. I have experience building production-ready applications and contributing through GitHub workflows. I'll deliver a reliable, well-tested solution with clean, maintainable code

[444notdotun]

Hi,

With 4 years of hands-on experience across backend, frontend, and smart contract development, I'm confident I can complete this task quickly and to a high standard. I've reviewed the requirements in detail and fully understand what's needed.

My focus is on writing clean, efficient, and maintainable code backed by thorough testing and industry best practices. I'll ensure the solution is production-ready and delivered on time.

I expect to have my PR ready in less than 10 hours.

[leocagli]

I'd like to work on this, please assign me!