Skip to content

When putting a membership, a database conflict should be handled as a 200 no problem #40

@simen

Description

@simen

This should never need to be reported, as it means the membership exists allready

https://errbit.o5.no/apps/505252ff32a0ec3f160000af/problems/50b4fbff32a0ec28f600000d

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