Skip to content

Fix Replay Data Corruption for Non-JSON Payloads (#2813)#12

Open
deepshekhardas wants to merge 1 commit into
mainfrom
fix/2959-replay-data-corruption
Open

Fix Replay Data Corruption for Non-JSON Payloads (#2813)#12
deepshekhardas wants to merge 1 commit into
mainfrom
fix/2959-replay-data-corruption

Conversation

@deepshekhardas
Copy link
Copy Markdown
Owner

@deepshekhardas deepshekhardas commented May 24, 2026

Fixes replay data corruption for non-JSON payloads by:\n- Allowing non-JSON string payloads in replay (removing JSON.parse validation)\n- Detecting large payloads and preventing editing them\n- Properly showing tooltip for large vs store payloads\n\nCloses triggerdotdev#2959


Summary by cubic

Prevents replay data corruption for non-JSON payloads by allowing raw string payloads and making oversized or stored payloads read-only. Improves clarity in the replay dialog with accurate tooltips for large vs too-large payloads. Closes triggerdotdev#2959.

  • Bug Fixes
    • Accept any string payload in ReplayRunData (removed JSON validation) to preserve non-JSON data.
    • In Replay dialog, mark application/store and >512 KB payloads as read-only and show the correct tooltip.

Written for commit c7507f0. Summary will update on new commits. Review in cubic

Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

Re-trigger cubic

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.

1 participant