-
Notifications
You must be signed in to change notification settings - Fork 0
Rename snake_case query parameters to camelCase #41
Copy link
Copy link
Open
Labels
area: knowledgeKnowledge base, recall, capture, or curation.Knowledge base, recall, capture, or curation.component: apiHTTP API, OpenAPI contract, or API client concern.HTTP API, OpenAPI contract, or API client concern.priority: P3Low; backlog, cleanup, or opportunistic work.Low; backlog, cleanup, or opportunistic work.type: refactorCode structure change without intended behavior change.Code structure change without intended behavior change.
Description
Activity
Metadata
Metadata
Assignees
Labels
area: knowledgeKnowledge base, recall, capture, or curation.Knowledge base, recall, capture, or curation.component: apiHTTP API, OpenAPI contract, or API client concern.HTTP API, OpenAPI contract, or API client concern.priority: P3Low; backlog, cleanup, or opportunistic work.Low; backlog, cleanup, or opportunistic work.type: refactorCode structure change without intended behavior change.Code structure change without intended behavior change.
What to build
This service's query parameters are renamed to camelCase, matching every other service in the estate.
It is currently the only service using snake_case parameter names, which is why the estate cannot yet enforce a casing rule. This is a breaking contract change: it takes the generated clients to a new major version and every consumer must move in step.
Acceptance criteria
Blocked by