nextcloud / nextcloud/contacts
When importing contacts with identical UUIDs to existing contacts, prompt to replace them.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 642
- Forks
- 220
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 51
Description
Is your feature request related to a problem? Please describe.
As https://help.nextcloud.com/t/bug-cant-import-all-vcard-faulty-contacts/68058/9?u=rokejulianlockhart explains, if I export and then import my NextCloud contacts, I see a nondescript "error" for each contact.
Describe the solution you'd like
To prevent confusion, the exporter (and importer) should explain that the UUID field prevents these contacts being imported, unless they replace the contacts in the database.
Describe alternatives you've considered
No response
Additional context
Similar to https://github.com/nextcloud/contacts/issues/3981#issue-2353836354.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the contacts import and export flows to find where identical UUIDs are rejected and where the import error is presented. Review related issue 3981 and the linked help discussion for context. Done means the importer and exporter clearly explain the UUID conflict and prompt to replace existing contacts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100