nextcloud / nextcloud/contacts

Search using letters without diacritics (unaccented) doesn't show contacts containing letters with diacritics (accented) in results.

Open
#4,064 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug feature: contacts
Dominant language
JavaScript
Stars
642
Forks
220
Avg merge
14h 39m
Merged PRs (30d)
51

Description

Describe the bug

When searching using letters without diacritics (unaccented) doesn't show contacts containing letters with diacritics (accented) in results.

Steps to reproduce
  1. Create contact with first name "Álvaro" and save it.
  2. Click on 'Search contacts' input field.
  3. Put "Alvaro" or "alvaro" in the search field.
  4. See the result without the contact created on step 1.
  5. Enter "Álvaro" or "álvaro" in the search field.
  6. See the result containing the contact created on the step 1.
Expected behavior

When I enter "alvaro" in the search field I should see contact named "Álvaro" in the search results.

Actual behavior

When I enter "alvaro" in the search field I don't see contact named "Álvaro" in the search results.

Contact version

6.0.0

Operating system

Docker 24.0.2: nextcloud:29-fpm sha256:109d5ca081279b08ecc7d1061b019d62961ae80dcdeb34e333aa930a7b97f1dd

PHP engine version

Other

Web server

Nginx

Database

PostgreSQL

Additional info

PHP 8.2.21

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by reproducing the issue with a contact named “Álvaro” and an unaccented “Alvaro” query, then trace the contact search entry point and its PostgreSQL-backed search behavior. Done means unaccented searches return contacts containing the corresponding accented letters, while the existing reproduction steps pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, php, postgresql
Domain
backend, databases, search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.