-
Notifications
You must be signed in to change notification settings - Fork 3
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
fix:(SC-3376) Handle delete success/fail toasts on a per object basis #136
Conversation
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.
This all works well now.
aside from the annoying formatting warnings.
objectStore.ts now uses Promise.allSettled instead of Promise.all and returns an array of objects for each promise with their status. DeleteObjectButton.vue waits for the array and displays a toast based on each success or fail.
@@ -70,7 +70,7 @@ describe('Object Store', () => { | |||
|
|||
let createObjectSpy: SpyInstance; | |||
let deleteObjectSpy: SpyInstance; | |||
let fetchObjectsSpy: SpyInstance; | |||
// let fetchObjectsSpy: SpyInstance; |
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.
Not a big concern, just wondering why fetchObjectsSpy are commented and not removed?
Description
objectStore.ts now uses Promise.allSettled instead of Promise.all and returns an array of objects for each promise with their status.
DeleteObjectButton.vue waits for the array and displays a toast based on each success or fail.
Types of changes
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Checklist
Further comments
Deleting a list of 3 files looks as follows.