Skip to content

Params #3

@xentek

Description

@xentek
  • (Parsing Params #41) Params should be parsed in this order, with each subsequent source overwriting the previous value:
    • QueryString
    • Body (depends on content-type)
    • Path (e.g. /resources/{id})
  • (Custom Types for Params #43) Params should be discrete types, and have a Name and Description, to promote re-use.
  • (Allowed / Required Params #42) Params should be Optional or Required.
    • Params not allowed for a given request, should be dropped.
    • Required Params not present in request should cause a 400 Bad Input error to be returned.
  • (Bind Params to a given Endpoint #44) Params should be associated with a given Endpoint
    • Params should be method aware (as rules for optional/required, etc may differ between request methods)
    • Some Params, especially with GET requests may not be a part of a resource, but act as controls or filters for the requested data (e.g. search, date ranges, etc)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions