MR Review: improve UX when extension fails to create new comment
Problem to solve
We implemented creating comments on MR diff in #342 (closed).
The happy-path scenario works well, but when the comment fails to send (network failure, GitLab API unavailable) the UX is not great. We show the user an error message and store the comment text in extension logs, but we don't offer an easy way to retry sending the comment. Each failure has to be followed by copy-pasting the comment text from logs and trying again.
Proposal
We should handle the failure similarly to the GitHub Pull Request extension. We should create a new type of comment (failed comment) which would have a button to retry.
- Creating comment fails
- Extension creates a failed comment and puts it into the diff discussion
- The failed comment has a "Retry" button which lets users try to resend it
Current UX
Edited by Tomas Vik