Skip to content

Rename snake_case query parameters to camelCase #41

Description

@ExtraToast

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

  • No query or path parameter uses snake_case
  • The breaking change is landed deliberately, with the client major bump expected rather than surprising
  • Every consumer of the renamed parameters is updated
  • Export drift passes

Blocked by

  • Adopt the ProblemDetail customizer and re-export the spec

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: knowledgeKnowledge base, recall, capture, or curation.component: apiHTTP API, OpenAPI contract, or API client concern.priority: P3Low; backlog, cleanup, or opportunistic work.type: refactorCode structure change without intended behavior change.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions