task/WP-698: NCO text search made case insensitive #1478
Merged
+3
−3
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.
Overview:
Mongodb queries by default are case insensitive, and NCO requested, if possible, for it to be made case-insensitive.
PR Status:
Related Jira tickets:
Summary of Changes:
Added "i" flag to the regex queries that are part of the text search field to make them case-insensitive.
Testing Steps:
UI Photos:
Notes:
Need to be on the vpn for the connection to the nco mongodb to work.
Also, this solution will work, but if the database grows much larger, this could cause the searches to become slow. However, due to how the search needs to be run, there's no way around this from my research.