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
Date discovered
9/30/2026
Did you have to do something temporarily
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
Recommended Action Items
Potential solutions [draft]
- Update
filterNameSingular inside noResultMessageComponent function 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.
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
Date discovered
9/30/2026
Did you have to do something temporarily
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
toggleNoResultMsgIfNoMatch.toggleNoResultMsgIfNoMatchusesnoResultMessageComponentfunction from assets/js/elements/noResultsMessageFilter.jsRecommended Action Items
Potential solutions [draft]
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.