tristan-orourke commented 7 months ago

✨ Feature

User and PoolCandidate name/email/general search treats accented characters uniquely. However, this can create confusion, especially when it comes to names, which people may choose to type with or without accents, somewhat arbitrarily. Like we've done in client-side search and sort features, it would be much better for users if we treated accented and non-accented characters the same.

🕵️ Details

In search, all accented versions of a character should be like the non-accented version. This should apply to the text being searched as well as the user input.

🎨 Design File

None

🧑‍🎨 Designer

@Jerryescandon

🙋‍♀️ Proposed Implementation

If it is very difficult to apply this to the general search, at the very least it should apply to names and emails. That may be easier after #9956.

https://www.postgresql.org/docs/current/textsearch-dictionaries.html

🌎 Localization

(optional) Provide any new copy along with translations available.

✅ Acceptance Criteria

A set of assumptions which, when tested, verify that the feature was properly implemented.

[ ] search bar input in user and pool candidate tables ignores accents when matching names and emails
[ ] Optional: search input also ingores accents for general text search matching

🛑 Blockers

Issues which must be completed before this one.

### Blocked By
- [ ] #9956

github-actions[bot] commented 7 months ago

Status: Ready to merge :heavy_check_mark:

Issues blocking this PR:

9956 :heavy_check_mark:

This comment was automatically written by the Blocking Issues bot, and this PR will be monitored for further progress.