[Feature] Define shared contact connector diagnostics and dry-run contracts #8

Open
opened 2026-07-13 00:53:54 +02:00 by zemion · 0 comments
Owner

Goal

Keep address-book connectors aligned with the platform connector runtime while allowing govoplan-addresses to own contact semantics.

Scope

  • shared connector diagnostics shape for address sync
  • dry-run/preview contract for creates, updates, deletes, and conflicts
  • credential and endpoint settings patterns reused from other connector surfaces
  • clear boundary between connector runtime and address/vCard semantics

Acceptance Criteria

  • CardDAV/LDAP/Exchange/Google address connectors can report diagnostics consistently.
  • govoplan-addresses owns vCard/contact mapping; govoplan-connectors owns shared connector runtime patterns.
  • Future connector modules can reuse dry-run and diagnostics contracts.

Related address-module plan: govoplan-addresses/docs/IMPLEMENTATION_PLAN.md.

## Goal Keep address-book connectors aligned with the platform connector runtime while allowing `govoplan-addresses` to own contact semantics. ## Scope - shared connector diagnostics shape for address sync - dry-run/preview contract for creates, updates, deletes, and conflicts - credential and endpoint settings patterns reused from other connector surfaces - clear boundary between connector runtime and address/vCard semantics ## Acceptance Criteria - CardDAV/LDAP/Exchange/Google address connectors can report diagnostics consistently. - `govoplan-addresses` owns vCard/contact mapping; `govoplan-connectors` owns shared connector runtime patterns. - Future connector modules can reuse dry-run and diagnostics contracts. Related address-module plan: `govoplan-addresses/docs/IMPLEMENTATION_PLAN.md`.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-connectors#8
No description provided.