nextcloud / nextcloud/contacts
Warn the user when exporting contacts, which shall cause errors when imported.
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://github.com/nextcloud/contacts/issues/3980#issue-2353834244 explains, common features of contacts which the database supports but the importer does not can cause valid contacts to become unimportable.
Describe the solution you'd like
So that the user does not need to ascertain how to manually modify their exported .VCF to get it importable again, the exporter should warn the user when exporting shall cause unimportable contacts to be created.
Describe alternatives you've considered
No response
Additional context
Similar to https://github.com/nextcloud/contacts/issues/990#issue-419691662.
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 contact exporter and importer behavior described in this issue, then read the linked issues for examples of valid contacts that become unimportable. Done means exporting such a contact warns the user before producing an unimportable VCF, without requiring manual edits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100