Skip to content

Prevent multiple competing endpoint definitions #19

Description

@myronmarston

Currently interpol allows one endpoint definition file to contain multiple competing definitions: e.g. 2 response definitions for the same version. This can cause problems. Ideally, interpol should raise an error when an Endpoint is instantiated with a data hash like this. Note that it needs to be able to handle definitions that vary by status code, so that should be taken into account as well.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions