Add optimistic UI updates to dialogs mutations

[mikewheeleer]

Optimistic dialogs

Description

dialogs mutations wait for the server before updating the UI, feeling sluggish. This issue adds optimistic updates with rollback.

Requirements and context

• Repository scope: Talenttrust/Talenttrust-Frontend only.
• Apply dialogs mutations optimistically and roll back on error with a clear message.
• Guard against stale overwrites.
• Cover success and rollback in tests.

Suggested execution

• Fork the repo and create a branch
• git checkout -b feature/dialogs-61-optimistic
• Implement changes
  • Write code in: the relevant module.
  • Write comprehensive tests in: cover the new behaviour and edge cases.
• Test and commit

Test and commit

• Run npm run lint, npm test, and npm run build.
• Cover edge cases: success keeps update, error rolls back.
• Include the full test output in the PR description.

Example commit message

feat(dialogs): optimistic updates

Guidelines

• Minimum 95 percent test coverage for impacted modules.
• Clear, reviewer-focused documentation.
• Timeframe: 96 hours.

Community & contribution rewards

• 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
• ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated.

[drips-wave]

@mikewheeleer This issue could not be added to the Stellar Wave Program because the per-repo points budget would be exceeded (25000 / 25000 points already used). The label has been automatically removed.

The budget resets at the end of each Wave. You can review the remaining budget for your repos on the Orgs & Repos page.

ℹ️ Learn more about points budgets

[angelraph]

I'd like to work on this issue.

I've built and maintained React, Next.js, and TypeScript applications where perceived responsiveness is just as important as correctness. Optimistic updates are one of those areas where it's easy to make the interface feel faster, but much harder to ensure state remains consistent when requests fail, complete out of order, or overlap. My focus would be delivering an implementation that is both responsive and resilient.

I'll begin by reviewing the existing dialogs mutation flow to understand how state is managed and where optimistic updates fit naturally within the current architecture. Rather than introducing a parallel state path, I'll build on the existing data flow so the optimistic state, server reconciliation, and rollback behavior remain predictable and easy to maintain.

The implementation will optimistically update the UI immediately after a mutation is initiated, preserve the previous state for reliable rollback, and guard against stale responses overwriting newer user actions. I'll also ensure failures surface clear, actionable feedback without leaving the interface in an inconsistent state. Where appropriate, I'll use the project's existing caching and invalidation strategy instead of introducing unnecessary complexity.

Alongside the implementation, I'll add comprehensive tests covering successful optimistic updates, rollback on failure, concurrent mutation scenarios, and stale response handling to ensure the behavior remains reliable as the application evolves. Before opening the PR, I'll run linting, the full test suite, and a production build to verify the changes integrate cleanly with the existing codebase.

My goal is to improve the responsiveness of the dialogs experience while preserving data integrity, keeping the implementation aligned with the project's patterns, and leaving maintainers with code that's straightforward to review and extend.