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

[TASK] Make search in file module case-insensitive #119

Conversation

dreistromlandMf
Copy link
Contributor

The JavaScript-Based search in the file module is case sensitive. This is unusual for searches.

Both the searched value as well as the searchable data are now transformed toLowerCase before comparison.

Possible improvements are:

  • Applying that transformation in Fluid, trading having it to do every request server-side vs. not having to do it on the client for every search.
  • Implementing some kind of fuzzy search-logic.

dhoffmann1979 and others added 4 commits May 2, 2024 14:29
The JavaScript-Based search in the file module is case sensitive. This
is unusual for searches.

Both the searched value as well as the searchable data are now
transformed toLowerCase before comparison.

Possible improvements are:
 - Applying that transformation in Fluid, trading having it to do every
   request server-side vs. not having to do it on the client for every
   search.
 - Implementing some kind of fuzzy search-logic.
@dreistromlandMf dreistromlandMf marked this pull request as ready for review August 29, 2024 07:40
@sbusemann
Copy link
Contributor

@pixeldesu pixeldesu changed the base branch from master to develop September 25, 2024 12:18
@pixeldesu
Copy link
Member

pixeldesu commented Sep 25, 2024

Thanks for your contribution! Manually cherry-picked this into develop at 33242ec due to previous master commits being present in this PR for some reason.

Also, please open Pull Requests against our default (develop) branch, not the master branch.

@pixeldesu pixeldesu closed this Sep 25, 2024
@dreistromlandMf
Copy link
Contributor Author

There being commits unmerged into develop is exactly why I switched it. I'll try to rebase onto develop if there is a next time 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants