Skip to content

feat: use exn said as the notification id - #14

Open
Sotatek-Patrick-Vu wants to merge 1 commit into
release/v1.3-idwfrom
feat/exn-said-notification-id
Open

feat: use exn said as the notification id#14
Sotatek-Patrick-Vu wants to merge 1 commit into
release/v1.3-idwfrom
feat/exn-said-notification-id

Conversation

@Sotatek-Patrick-Vu

Copy link
Copy Markdown
Collaborator

Uses the SAID as the notification id, so a re-delivered exn produces one notification instead of one per delivery.

# a second notice for the same exn keeps the id even though the datetime moves
other = notifying.notice(attrs=payload, rid=said, dt="2022-07-08T15:01:05.453632")
assert other.rid == said
assert other.datetime != note.datetime

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this impact notifications received on Signify side, or this is an internal test? (i.e. .add de-dups stopping this)

@iFergal

iFergal commented Sep 4, 2026

Copy link
Copy Markdown
Collaborator

@jimcase currently investigating what changes (if any) in Veridian Wallet required if we make this change (should be none I think)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants