ADR: API Naming Conventions
Status
Not Started
Context
We currently don't have any agreed naming conventions for API field names.
Server responses have largely been formatted ad hoc, which has lead to inconsistencies in response format and naming. This is going to increasingly become an issue as the team grows if we don't agree on conventions.
Decision
[To be defined]
Consequences
[To be defined]
Impact
Medium
Driver
@Marc North @Michal Kolek
Contributors
[Team]
Accepted Date
[Not started]