cleanup: simplify geocoding provider configuration #315

Closed
opened 2026-05-11 19:19:50 +00:00 by barrettruth · 1 comment
Owner

Parent: #305

Problem

Geocoding currently supports Photon plus token-backed providers through settings and test endpoints. That may be more provider surface than the blank-start app needs, and the provider rules are split across UI, route handlers, and integration config helpers.

Solution

Make the geocoding scope explicit and smaller:

  • decide whether v0.1 keeps Photon-only, Photon plus env-token provider, or full provider selection
  • centralize provider IDs, labels, required fields, and test behavior if multiple providers remain
  • remove settings/test UI for providers that are not part of v0.1
  • keep geocoding failures visible but non-blocking for task creation/editing

Acceptance criteria

  • The settings UI exposes only supported geocoding behavior.
  • /api/geocode and provider test routes use the same provider contract.
  • No paid-provider credential is required for a fresh blank-start instance.
  • Tests cover the selected provider fallback behavior.
Parent: #305 ## Problem Geocoding currently supports Photon plus token-backed providers through settings and test endpoints. That may be more provider surface than the blank-start app needs, and the provider rules are split across UI, route handlers, and integration config helpers. ## Solution Make the geocoding scope explicit and smaller: - decide whether v0.1 keeps Photon-only, Photon plus env-token provider, or full provider selection - centralize provider IDs, labels, required fields, and test behavior if multiple providers remain - remove settings/test UI for providers that are not part of v0.1 - keep geocoding failures visible but non-blocking for task creation/editing ## Acceptance criteria - The settings UI exposes only supported geocoding behavior. - `/api/geocode` and provider test routes use the same provider contract. - No paid-provider credential is required for a fresh blank-start instance. - Tests cover the selected provider fallback behavior.
barrettruth added this to the v0.1.0 milestone 2026-05-11 19:19:50 +00:00
Author
Owner

Product direction update: NLP and geocoding/mapping providers must stay. Do not solve this issue by making geocoding Photon-only or removing Mapbox/Google Maps support. The remaining #315 work should simplify/refactor provider configuration while preserving provider choices, credential handling, tests, and non-blocking fallback behavior.

Product direction update: NLP and geocoding/mapping providers must stay. Do not solve this issue by making geocoding Photon-only or removing Mapbox/Google Maps support. The remaining #315 work should simplify/refactor provider configuration while preserving provider choices, credential handling, tests, and non-blocking fallback behavior.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
barrettruth/delta#315
No description provided.