Skip to content

Invited reviewer updates for manuscript versions

Vaibhav Rathore requested to merge feature/1253/invited-reviewer-kanban into main

Targets #1253 (closed)

Summary

  1. Loading invitations for each version within the main get_manuscript response instead of querying for invitations separately. The existing query was only querying for the latest manuscript and not for previous versions.
  2. Instead of refetchQueries after mutation, the system is refetching the whole manuscript object, thus getting the new invitations for the latest version.
  3. When getting the invitation status to accept/decline invitation, the code will check if the queried invitation is for the latest manuscript version or not. If not, then the invitation is sent as expired to frontend.
  4. We do not need to update the invitation status in the database as the "unanswered" invitations are being used in the Kanban to show pending invitations in previous versions.
  5. Invitation will be stored in local storage only if the status is "unanswered". This avoids saving any unintentional data into local storage that may then be used by login or some other page.

Merge request reports