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

Feature: an erase option for drivers (delete keeps personal data in the rows)

Offen
  • Stimmt etwas nicht?
#369 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
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
php
Bereich
api, backend, database

Rechercherichtung

Start by tracing DELETE /v1/drivers/{id} through ProfileAccountManager::releaseForProfile() and inspect how driver orders, activity rows, positions, and request logs are stored and referenced. The issue proposes several possible erase semantics but does not settle how to handle retained orders and proofs or request logs. Done would require an agreed erase behavior that removes personal data while preserving the specified delivery history and leaving staff accounts alone.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Is your feature request related to a problem? Please describe.

DELETE /v1/drivers/{id} soft-deletes the driver and, through ProfileAccountManager::releaseForProfile(), soft-deletes its managed user. Both rows keep the person's name, email, phone, username and last location. The update endpoint can't clear all of it first (username, for example), and activity rows and api_request_logs still hold the original contact details.

Deployments that must honor a deletion request (GDPR, CCPA, app store account deletion rules) have no API way to remove a driver's personal data.

Describe the solution you'd like

An erase option, for example DELETE /v1/drivers/{id}?erase=true or POST /v1/drivers/{id}/erase, that hard-deletes the driver and its managed login user (staff accounts left alone, as today), removes their activity rows and the driver's positions, and keeps orders and proofs, with the driver reference kept or pointed at a placeholder.

Separately, the soft delete sets driver_assigned_uuid to NULL on the driver's orders, including completed ones, so delivery history loses who made the delivery. That may be worth keeping.

Describe alternatives you've considered

Overwriting the fields with PUT before DELETE, which is what we do now. It leaves the username, activity rows and request logs behind.

Additional context

This would let Fleetbase be used for driver programs where deletion on request is a legal requirement. If you want it, we can send the PR. Fleetbase v0.7.68 (fleetops 0.6.71, core-api 1.6.68).

Vorherrschende Sprache
PHP
Sterne
40
Forks
72
Ø Merge
19 Std.
Gemergte PRs (30 T.)
66

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 fleetbase/fleetops

Alle Issues in fleetbase/fleetops

Ähnliche Issues

Weitere Issues zu PHP

Neue Issues direkt in Ihr Postfach

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