Gleipnir/nidus-sync
4
0
Fork 0
Code Issues 20 Pull requests Projects Releases Packages Wiki Activity Actions

Staging: Failed to tell user when notification save didn't work #28

New issue
Open
opened 2026-05-24 21:00:02 +00:00 by eliribble · 2 comments
eliribble commented 2026-05-24 21:00:02 +00:00
Owner
Copy link

See #27 - when the API fails to save notifications, we don't show the user an error, and we should.

See #27 - when the API fails to save notifications, we don't show the user an error, and we should.
eliribble commented 2026-05-24 21:40:50 +00:00
Author
Owner
Copy link

Hmm, seems like we do show an error, I didn't even change anything...

Hmm, seems like we do show an error, I didn't even change anything...
Screenshot 2026-05-24 at 14.40.12.png
121 KiB
Screenshot 2026-05-24 at 14.40.12.png
tzipporahribble was assigned by eliribble 2026-05-24 21:41:01 +00:00
eliribble commented 2026-05-24 21:41:29 +00:00
Author
Owner
Copy link

Tzipporah - please test this by adding some nonsense data to the "Report Successfully Submitted" page and making sure it complains appropriately.

Tzipporah - please test this by adding some nonsense data to the "Report Successfully Submitted" page and making sure it complains appropriately.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
0.0.14
0.0.13
0.0.12
0.0.11
0.0.10
0.0.9
0.0.8
0.0.7
v0.0.6
v0.0.3
v0.0.2
v0.0.1
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
tzipporahribble
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Gleipnir/nidus-sync#28
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?