david.delagneau
1ad707373a
- Created daily log entries for May 13, 14, 18, 19, 20, and 21, capturing work done, findings, and next steps. - Established a daily logs index for easy navigation of daily notes. - Developed templates for daily logs, decisions, meeting notes, people, systems, and work items to standardize documentation. - Introduced base files for filtering and displaying various types of project knowledge, including daily notes, decisions, people, systems, work items, and workstreams. - Added maps for current work, fidelity apps, and fidelity domain to enhance project navigation and context.
41 lines
668 B
Markdown
41 lines
668 B
Markdown
---
|
|
type: decision
|
|
project: fidelity
|
|
status: accepted
|
|
title: "REST vs GraphQL"
|
|
updated: 2026-04-16
|
|
tags:
|
|
- decision
|
|
- fidelity
|
|
---
|
|
# REST vs GraphQL
|
|
|
|
## Decision
|
|
|
|
Deprecate GraphQL and migrate to REST progressively.
|
|
|
|
---
|
|
|
|
## Constraints
|
|
|
|
- REST is behind a feature flag
|
|
- GraphQL remains fallback
|
|
- Behavior parity matters during migration
|
|
|
|
---
|
|
|
|
## Communication Rule
|
|
|
|
When reporting findings:
|
|
|
|
- state whether REST was confirmed enabled
|
|
- avoid implying REST is the default path
|
|
- call out when behavior may still come from GraphQL fallback
|
|
|
|
---
|
|
|
|
## Follow-up
|
|
|
|
- Remove Apollo when migration is safe
|
|
- Retire GraphQL-specific tests only after parity is confirmed
|