Skip to content

Conversation

@nithish-74
Copy link

@nithish-74 nithish-74 commented Oct 28, 2025

Closes #999

  • backend optimistic-locking (version field, 409 conflict)
  • frontend conflict toast + auto-retry
  • Cypress coverage for two-tab race

@nithish-74 nithish-74 marked this pull request as ready for review October 28, 2025 12:20
@nithish-74 nithish-74 closed this Oct 28, 2025
@nithish-74 nithish-74 force-pushed the feat/999-optimistic-locking branch from 5700d29 to 8189bc7 Compare October 28, 2025 12:24
@nithish-74 nithish-74 deleted the feat/999-optimistic-locking branch October 29, 2025 09:12
@nithish-74 nithish-74 restored the feat/999-optimistic-locking branch October 29, 2025 09:14
@nithish-74 nithish-74 deleted the feat/999-optimistic-locking branch October 29, 2025 09:14
@nithish-74 nithish-74 restored the feat/999-optimistic-locking branch October 29, 2025 09:14
@nithish-74 nithish-74 reopened this Oct 29, 2025
@nithish-74
Copy link
Author

@marcgc21 could you please review and approve when convenient?
All checks are green — optimistic-locking implementation complete.

@nithish-74 nithish-74 force-pushed the feat/999-optimistic-locking branch from ca8d176 to 5700d29 Compare October 29, 2025 09:54
@sonarqubecloud
Copy link

@sahitya-chandra
Copy link
Member

@nithish-74, thanks for your contribution. This PR clearly doesn't solve the issue. So, closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: when two or more study admins are editing one study, who saves first overwrite other works

2 participants