ER: [Toolkit Page]: Fix "undefined" message shown when filter selects no guide or resource cards
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start with toggleNoResultMsgIfNoMatch in assets/js/toolkit.js and trace its use of noResultMessageComponent in assets/js/elements/noResultsMessageFilter.js. Check how the shared function is used by current-projects.js before making the change. Done means the toolkit no-results message shows the filter category, such as "Tools: Github", instead of "undefined: Github" without breaking the other page.
Written by the indexing model from the issue text.
Description
Emergent Requirement - Problem
On toolkit page, when applying filters to search for guide or resource cards, if no results match the selected criteria, the page displays the message "we couldn't find results for:" followed by the filter information. However, the filter label is missing and shows as undefined: Github instead of the expected category name like Tools: Github.
Issue you discovered this emergent requirement in
- #8558
Date discovered
9/30/2026
Did you have to do something temporarily
- YES
- NO
Who was involved
@Tomomi-K1
What happens if this is not addressed
When users apply filters that return no matching guide or resource cards, they see a confusing error message displaying undefined: Github instead of a clear filter label like Tools: Github. This creates a poor user experience. Without fixing this, users cannot effectively troubleshoot their searches or understand why no results appeared.
Resources
- pages/toolkit.html : Toolkit Page
- Function that handles showing no result message can be found on assets/js/toolkit.js: Function name is
toggleNoResultMsgIfNoMatch. toggleNoResultMsgIfNoMatchusesnoResultMessageComponentfunction from assets/js/elements/noResultsMessageFilter.js
Recommended Action Items
- Make a new issue
- Discuss with team
- Let a Team Lead know
Potential solutions [draft]
- Update
filterNameSingularinsidenoResultMessageComponentfunction to properly handle cases with toolkit page but also need to double check with how this function is also used in current-projects.js and make sure it works for both. Or we could make separate function for each.
- Dominant language
- JavaScript
- Stars
- 364
- Forks
- 871
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 13
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 hackforla/website
-
good first issue P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt time sensitive
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Feature: Code Alerts good first issue P-Feature: Project Info and Page role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 Under an hour Newbie friendliness 90/100
hackforla/website#8825 · 1 comment ·
Maintainers usually reply within 1 day
-
Feature: Code Alerts good first issue P-Feature: Project Info and Page role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Feature: Code Alerts good first issue P-Feature: Project Info and Page role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Complexity: Small non-PR contribution P-Feature: Projects page ready for merge team role: back end/devOps size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
hackforla/website#8822 · 1 comment ·
Maintainers usually reply within 1 day
All issues in hackforla/website
Similar issues
-
component:sight
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agentic-os-org/ANOLISA#6738 · 2 comments ·
Maintainers usually reply within 1 day
-
bug Durable Agents Observability (AI Telemetry) status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
mastra-ai/mastra#26470 · 1 comment ·
Maintainers usually reply within 1 day
-
feature/cohorts feature/feature-flags team/feature-flags
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Orbit-xyz/orbit-docs#11 ·
-
area/build area/tech debt
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days