Page MenuHomePhabricator

When a new, deleted, draft inline is revived with "Undo", undelete it
ClosedPublic

Authored by epriestley on Oct 19 2020, 7:31 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Mar 27, 2:02 AM
Unknown Object (File)
Thu, Mar 7, 7:32 PM
Unknown Object (File)
Feb 8 2024, 6:22 PM
Unknown Object (File)
Jan 9 2024, 8:02 AM
Unknown Object (File)
Dec 27 2023, 1:39 PM
Unknown Object (File)
Dec 26 2023, 5:42 PM
Unknown Object (File)
Dec 22 2023, 3:26 AM
Unknown Object (File)
Dec 20 2023, 12:18 AM
Subscribers
None

Details

Summary

See PHI1876. Normally, deleted inlines are undeleted with an "undelete" operation, which clears the "isDeleted" flag.

However, when an inline is deleted implicitly by using "Cancel" without first saving it, the flag currently isn't cleared properly. This can lead to cases where inlines seem to vanish (they are shown to the user in the UI, but treated as deleted on submission).

Test Plan

There are two affected sequences here:

  • Create a new inline, type text, cancel, undo.
  • Create a new inline, type text, cancel, undo, save.

The former sequence triggers an "edit" operation. The subsequent "Save" in the second sequence triggers a "save" operation.

It's normally impossible in the UI to execute a "save" without executing an "edit" first, but "save" clearly should undelete the comment if you get there somehow, so this change clears the deleted flag in both cases for completeness.

  • Executed both sequences, saw comment persist in preview, on reload, and after submission.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable