Fix/different result for trailing spaces #106
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
ellazhuu
requested review from
haram082,
ksantoso2 and
PrinceBashangezi
and removed request for
haram082
ellazhuu
changed the title
haram082
approved these changes
Sep 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
context: the search was including trailing spaces in its query. For instance, "history" and "history " returned different results.
fix: I called .trim() on the search term before passing it into the backend query. This removes spaces from both the beginning and end of words, but not the middle.
demo: previously, searching history with many trailing spaces would not return any matches because it was performing a literal search for those spaces. now, the two returns the same results.
