Skip to content

path versus body convention in APIs #3

@eric-jahn

Description

@eric-jahn

We need to set an api convention that were don't have parameters in the request body when they are already in the path variable. Having both can cause issues, as we've seen. Like, if they are inconsistent, or if they are critical but not enforced in the body, etc... Thus issue should be removed from all our apis.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions