Skip to content

Document the approach for ensuring notification creation is idempotent #141

@jongeorge1

Description

@jongeorge1

We should document the method we've used to ensure notification creation is idempotent.

#140 raised a discussion on whether the current mechanism a) is the best approach, and b) works. Much of this would have been bypassed if there was already an explanation of what's been implemented, as it is spread across multiple layers of the solution.

We should extract the current approach into an ADR which we can then review and use to identify any changes in approach required.

We should also add new specs at the API level to document/demonstrate the expected behaviour.

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