nextcloud / nextcloud/contacts

Allow marking a field as deprecated.

Open
#3,827 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement
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.

I frequently need to retain outdated e-mail addresses and telephone numbers in order to correspond historical correspondence to a contact, but need to mark that information as superceded.

Describe the solution you'd like

Allow me to mark a field and its data as deprecated.

Describe alternatives you've considered

I can use the field name, but it doesn't synchronize nor display consistently, and requires a significant amount of manual effort on my part.

Additional context

No response

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

The issue names no files, tests, or entry points, so first trace how contact fields are stored, synchronized, and displayed in the JavaScript app. Clarify the representation and UI behavior for deprecated fields, then add coverage for consistent synchronization and display of the deprecated status.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.