-
Notifications
You must be signed in to change notification settings - Fork 67
Add shared entry batch actions in collections navigation #3334
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
base: main
Are you sure you want to change the base?
Conversation
|
📦 Statoscope quick diff with main-branch: ⏱ Build time: -660 ms (-1.2%) ⚖️ Initial size: 0.56 kb (0.01%) 🕵️ Validation errors: 0 Full Statoscope report could be found here |
|
|
|
| deleteCollectionsPromise, | ||
| deleteWorkbooksPromise, | ||
| deleteSharedEntriesPromise, | ||
| ]).then((response) => { |
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.
A few notes on this part of the code:
Promise.alldoesn't handle exceptions. If one of the promises throws an error, the whole thing will fail because you haven't defined a catch block. If you don't care about the errors, you should usePromise.allSettledinstead.- Style-wise, it's better to use either callback syntax or async/await. In your case, you should store the
Promise.allresult in a variable and await the resolution of the promises.
Are there any plans to display errors for entities that failed to be deleted in the future?
| ); | ||
| } | ||
|
|
||
| await Promise.all([moveCollectionsPromise, moveWorkbooksPromise, moveEntriesPromise]); |
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.
The same question like for handleDelete action
No description provided.