Page MenuHomePhabricator

Formally track "initial", "committed", and "active" states for inline comments
ClosedPublic

Authored by epriestley on Mar 25 2021, 9:10 PM.
Tags
None
Referenced Files
F14399928: D21653.diff
Sun, Dec 22, 6:13 PM
F14393896: D21653.id51546.diff
Sun, Dec 22, 1:16 AM
Unknown Object (File)
Fri, Dec 20, 10:39 PM
Unknown Object (File)
Mon, Dec 9, 1:02 AM
Unknown Object (File)
Thu, Dec 5, 2:12 AM
Unknown Object (File)
Sat, Nov 30, 7:13 PM
Unknown Object (File)
Wed, Nov 27, 10:43 PM
Unknown Object (File)
Wed, Nov 27, 7:26 AM
Subscribers
None

Details

Summary

Ref T13559. Various client decisions depend on the "initial" or "committed" states of inline comments. Previously, these were informally constructed from "mostly similar" available values, or glossed over in some cases.

On the server, save the initial state when creating a comment. Save the committed state when applying a "save" operation. Send all three states to the client.

On the client, load and track all three states explicitly.

Test Plan

Created inlines, etc. See followups.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.Mar 29 2021, 4:01 PM
This revision was automatically updated to reflect the committed changes.