-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Add missing warning modals for re-exporting and retracting exported reports #82885
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
b22583e
Add missing warning modals for re-exporting and retracting exported r…
MelvinBot 1fc5bf6
Merge remote-tracking branch 'origin/main' into claude-fixExportRetra…
MelvinBot d8f9130
Fix: Sort imports in getClipboardTextTest.ts to match Prettier config…
MelvinBot 34b2fc5
Merge main into branch to resolve conflicts in markAsManuallyExported
MelvinBot 638147a
Fix: Restore prior export state on exportToIntegration failure
MelvinBot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In
exportToIntegration(), the failure path always writesisExportedToIntegration: false, which is incorrect when the user is re-exporting a report that was already exported. If the write fails (for example offline or transient network error), this clears the exported flag in Onyx even though the report is still exported, andReportUtils.isExported()will trust that false value over action history, so follow-up safeguards (like re-export/reopen warnings) stop appearing until state is re-synced. Please preserve and restore the previous value (similar tomarkAsManuallyExported) instead of hard-codingfalse.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MelvinBot Fix this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 638147a. Changed
exportToIntegration()to capturepreviousExportedValuefrom Onyx before the optimistic update and restore it in failure data, matching the pattern already used inmarkAsManuallyExported().