Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Improve Search Experience: Show 'No Results Found' When Query Yields No Matches #116

Open
1 task
Arinzelight opened this issue Oct 6, 2024 · 2 comments
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work

Comments

@Arinzelight
Copy link

Problem

When a user performs a search in search-index.html, there is no feedback or message displayed if no items match the search query. This can lead to confusion for users, as they might not realize that the search did not yield any results.

Description

A "No results found" message should be displayed when a search query returns no matches. This feature will provide clear feedback to users, improving the search experience by ensuring that users know when their search did not find any results.

Alternatives

An alternative could be to clear the search results area when no matches are found, but this approach might not provide as much clarity to the user. Showing a "No results found" message is a more user-friendly solution, as it explicitly informs the user of the search outcome.

Implementation

  • I would be interested in implementing this feature.
@Arinzelight Arinzelight added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Oct 6, 2024
@possumbilities possumbilities added 🚧 status: blocked Blocked & therefore, not ready for work and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Oct 7, 2024
@possumbilities
Copy link
Contributor

@Arinzelight As this is a framework, it does account for a dynamic implementation to output such a message within the body area.

I don't see a way to show that level of dynamic behavior that would be present once implemented into something like WordPress.

I am going to move this to status: blocked because as we expand the specimens this might be a good use-case for a specimen that displays a "zero-case".

@egbadon-victor
Copy link
Contributor

Hi @possumbilities

From what you suggested, does that we can raise an issue, implementing a specimen that displays a "zero case" ? This would be a way of validating the need for such a generic specimen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work
Projects
Status: Backlog
Development

No branches or pull requests

3 participants