Block a user
Add Sigit ID as a path param
Can you please add update the description of the PR with its primarily objective and what changes have been made?
fix: processing gift wraps and notifications
The next building block would be to ensure that subscriptions stay open while the user is using the app, but for now this should fix a high-priority issue, so it looks good.
89f6cd1dbe
feat(renotifications): can re-notify users on the signing page
9cefdad3fc
refactor: logs npubs for failed notifications
de7a8a868a
feat(notificiations): initial changes to check notifications per each user
b965623a02
refactor: updates error handling
Create Page - Save Draft Sigit State Locally
Create Page - 'Add User' UI Changes
Sign Page - User Can Sign Directly From the Marking Screen
Sigit Routing - Add Sigit ID as a Path Param
fix: load screen on sign, block on missing counterpart
A promise doesn't need to be awaited if chaining is used.
fix: load screen on sign, block on missing counterpart
I wonder if this flow should be refactored, given our recent conversation about error handling. I also thing that there are more efficient ways to handle loading state changes.
9dc160e89c
Merge pull request 'Signing Order' (#167) from issue-158 into staging
ec305c417b
fix: signing order