Page MenuHomePhabricator

Continue lifting column layout logic out of ColumnPositionQuery
ClosedPublic

Authored by epriestley on Feb 3 2016, 7:07 PM.
Tags
None
Referenced Files
F14048291: D15175.id36633.diff
Thu, Nov 14, 7:22 AM
F14045706: D15175.id36643.diff
Wed, Nov 13, 8:36 AM
F14036113: D15175.id36633.diff
Sun, Nov 10, 8:34 AM
F14013551: D15175.id36633.diff
Sat, Nov 2, 7:41 AM
F13987897: D15175.diff
Mon, Oct 21, 12:05 PM
F13977739: D15175.id.diff
Oct 18 2024, 7:49 PM
F13965185: D15175.id36633.diff
Oct 16 2024, 12:28 AM
Unknown Object (File)
Oct 13 2024, 6:53 AM
Subscribers
None

Details

Summary

Ref T10010. See D15174. This gets rid of the "actually apply the change" callsite and moves it to layout engine.

Next up is to make the board view use the layout engine, then throw away all the whack code in ColumnPositionQuery, then move forward with D15171.

Test Plan
  • Dragged tasks within a column.
  • Dragged tasks between columns.
  • Dragged tasks to empty columns.
  • Created a task in a column.
  • Swapped board to priority sort, dragged a bunch of stuff all over.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Continue lifting column layout logic out of ColumnPositionQuery.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
  • Remove giant debugging block.
chad edited edge metadata.

Will all this stuff be testable?

This revision is now accepted and ready to land.Feb 3 2016, 7:50 PM

Yeah, that's one of the big advantages of doing it this way. A big part of this is ultimately UI stuff so there are limits to how much I can reasonably cover, but the basic "moving stuff around" operations should be fairly testable once I get the new thing in place.

This revision was automatically updated to reflect the committed changes.