-
Notifications
You must be signed in to change notification settings - Fork 26
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
fix: Force All Contents Table Searches to Lower Case #2159
fix: Force All Contents Table Searches to Lower Case #2159
Conversation
…if present
… present
…if present
…-should-not-be
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #2159 +/- ##
==========================================
- Coverage 97.68% 97.66% -0.03%
==========================================
Files 690 690
Lines 7697 7703 +6
Branches 1819 1822 +3
==========================================
+ Hits 7519 7523 +4
- Misses 176 177 +1
- Partials 2 3 +1
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Codecov Report
@@ Coverage Diff @@
## main #2159 +/- ##
=======================================
- Coverage 97.69 97.66 -0.03
=======================================
Files 690 690
Lines 7697 7703 +6
Branches 1819 1822 +3
=======================================
+ Hits 7519 7523 +4
- Misses 176 177 +1
- Partials 2 3 +1
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
✅ Deploy Preview for gazebo-staging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you play around with this to ensure we're not case sensitive on the API? I don't think we are but worth double checking
We definitely are limited on the API side as well it seems. |
Hi @nicholas-codecov. I have been following this PR - is there any progress? It is not clear if search is still case sensitive, however it maps to lowercase search? For example, if there are these two files: |
Hi @nikosatwork! I'm not 100% certain as to the logic on the backend and how they're doing the filtering in the DB query. This PR here makes things worse as the backend is searching in a case-sensitive manner currently. The progress can be followed here on those changes. Once they're merged in this PR may not actually be needed because they will handle all of the conversion to lower case and filtering. |
I think that PR makes more sense - thank you for the update Nicholas |
No problem! |
Hey @nikosatwork, just giving you a quick heads up that this issue has been resolved in the API and should be functioning fully. |
Description
This PR closes #2157 by forcing all search param strings to lower case before sending to the API so that if the user so the search value param matches that of the requesting user.
Notable Changes
*ContentsTables
hooks to send search param string to lower case.