Make "references" terminology consistent · Issue #23 · astm-utm/Protocol · GitHub
Skip to content

Make "references" terminology consistent #23

Description

@BenjaminPelletier

Currently, the response for upserting a Subscription names the fields for pre-existing relevant Entities as "operations" and "constraints". For consistency with the rest of the API, these fields should be named "operation_references" and "constraint_references".

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