feat: Implement peer review workflow
Created by: Edouard-Legoupil
This commit introduces a new peer review workflow, allowing users to save draft reviews and automatically transitioning the proposal to the "Pre-Submission" stage.
Key changes:
-
Added a
save-draft-reviewendpoint to save a draft of a peer review. -
Modified the
submit_reviewendpoint to handle both draft and final submissions. -
Updated the
get_proposals_for_reviewendpoint to differentiate between draft and completed reviews. -
Modified the
submit_reviewendpoint to check if all reviewers have completed their reviews and, if so, change the proposal status to "Pre-Submission". -
Added a "Save as draft review" button to the
Review.jsxcomponent. -
Modified the
handleSubmitReviewfunction inReview.jsxto handle both "Save as draft" and "Peer review completed" actions. -
Updated the UI in
Dashboard.jsxto display "completed on: ..." for completed reviews. -
Modified the
Chat.jsxcomponent to display the peer review comments when the proposal is in the "Pre-Submission" stage. -
Does my code meet the quality standards for releasing packages?
-
Does the reviewer have all the information to validate the features/issues without too much research?
-
Does the customer who will validate the associated tickets have the information to do so without wasting time?
Issues to validate to close :
-
issue #
Processed issues to keep open or in progress:
-
issue #
Checklist:
-
Does the package check go local? -
Does the CI pass? -
Are the added / fixed features documented, tested? -
Are the added features / solved problems briefly presented in the PR message? -
Are the changes related to tickets / issues that I have listed in the commits and in the PR itself? -
Are the tickets in "review" mode in the Project Tracking Board? -
Does each ticket, if it is to be closed after acceptance of the PR, contain a comment that tells how to validate it?