Skip to content

Design system around api request options #17

Description

@wouter173

Currently api body's, path parameters and query params are specific per api endpoint and have different semantics. Make a standardised way to handle these 3 ways of inputting data into a request so it can be easily reused on all endpoint definitions.

Requirements:

  • Solution must handle body, path parameters, and query parameters.
  • Solution must handle camelCase => snake_case encoding for body.
  • Solution must handle path parameter encoding with Schema.fromJsonString for spec compliant parameters. (filters)
  • Solution should not require an effect.gen or effect.function.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions