Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Default contact source/storage options

Offen
#577 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
55/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Ruhig
Tech-Stack
android, kotlin
Bereich
mobile

Rechercherichtung

No files or tests are named; start by tracing the contact-creation flow and where storage options are selected and labeled. Done means new contacts use the requested default storage behavior and the storage labels distinguish app storage from phone/device storage.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

feature request needs triage
Checklist
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
  • This issue contains only one feature request.
  • I have read and understood the contribution guidelines.
Feature description

When adding a new contact it keeps defaulting to the default storage option set by the previous contacts app.
With that settings option, no need to keep it in contact fields when adding a new one.

Also it would be helpful to first time users if "Phone storage" is renamed to "App storage", then "local" to "Phone/Device storage". It would be super clear which is which and why one can't be accessed by other apps. Traditionally contacts on phone storage can be accessed by other apps when permitted.

Why do you want this feature?

For better UX

Additional information

No response

Vorherrschende Sprache
Kotlin
Sterne
917
Forks
73
Ø Merge
1 T. 16 Std.
Gemergte PRs (30 T.)
8

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus FossifyOrg/Contacts

Alle Issues in FossifyOrg/Contacts

Ähnliche Issues

Weitere Issues zu Kotlin

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.