-
-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature(locksmith): Decouple event creation from user connection state #15249
Conversation
fb4c227
to
94279c0
Compare
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
// This was a creation! | ||
if (created) { | ||
// Only send email if event is deployed | ||
if (created && event.status === EventStatus.DEPLOYED) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok let's make sure the email is still sent after it was deployed when this is happening later
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sure thing! good catch!
unlock-protocol#15249) * update model * add migration script * add event deployment status to types package * update event operations * update event controller * update event route * update unlockjs package * draft dashboard utilisation * update unlockjs * update operation * update controller * update model * update route * remove types * update controller * remove deprecated function * update controller * cleanup * remove deployment queue * linting * more cleanup * update to use package types
Description
This PR introduces a more reliable process for event creation by decoupling it from the user’s connection state during lock deployment. The previous implementation depended on the user witnessing the deployment, which was fragile in cases of disconnection or tab closure. The updated logic ensures events are consistently created regardless of the user’s connection status.
Issues
Fixes #15243
Refs #15243
Checklist: