Page MenuHomePhabricator

Clarify that 'order' is an optional parameter in Conduit API methods
ClosedPublic

Authored by epriestley on Jun 18 2015, 4:21 PM.
Tags
None
Referenced Files
F15579943: D13342.id32283.diff
Wed, May 7, 2:28 AM
F15566052: D13342.id.diff
Thu, May 1, 12:12 PM
F15549698: D13342.id32295.diff
Sun, Apr 27, 7:24 AM
F15539643: D13342.id.diff
Fri, Apr 25, 3:12 AM
F15538961: D13342.id32283.diff
Thu, Apr 24, 10:42 PM
F15535789: D13342.id.diff
Thu, Apr 24, 6:41 AM
F15531813: D13342.diff
Wed, Apr 23, 1:08 PM
F15525982: D13342.id32283.diff
Mon, Apr 21, 6:17 PM
Subscribers

Details

Summary

Fixes T8603. For automatic 'order' parameters provided by infrastructure en route to T7715, clarify that they are optional (we will use the default builtin order for the underlying Query if an order is not provided).

Test Plan

Used web UI to see "optional" hint.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Clarify that 'order' is an optional parameter in Conduit API methods.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
btrahan edited edge metadata.
This revision is now accepted and ready to land.Jun 18 2015, 7:33 PM
This revision was automatically updated to reflect the committed changes.