API access to Phabricator goodness.
Details
Tue, Feb 16
Yep, that's more constraints.
Nov 3 2020
- There is no way to pull custom field values with *.search. See above.
- There is no way to edit non-custom field values with *.edit. The underlying transactions haven't been modularized yet; they should be, then EditEngine should get appropriate EditField definitions.
- There's no way to identify which custom fields can be edited. This overlaps with T13248, but is also a Conduit API Console UI problem. The web UI should have some way to inspect parameter variations per object subtype for available subtypes.
- As a workaround, you can try to edit an invalid field. The error message will identify valid fields.
- There's no way to create steps with *.edit because you can't specify a step type. See T13449 for a general variation of the "type is required to initialize objects" problem.
HarbormasterBuildStepCoreCustomField emits no fields if a BuildStep has no attached Implementation object. This dates from D15352 and is conceptually reasonable ("don't crash if a build step exists but the implementation no longer does") but should probably be represented differently (e.g., an explicit "InvalidImplementation").
Sep 17 2020
Apr 15 2020
One possible improvement remains here: in streaming mode, HTTPSFuture will not "Accept-Encoding: gzip" and can not inflate responses. Today, this only applies to arc download.
Apr 14 2020
There's also one minor related concern in PHI1638 that I want to take care of here, since it's adjacent.
In fairness, "SetInputFilter DEFLATE" is documented as uniquely opinionated, if you catch this box and read between the lines a little bit:
A grand aventure in PHI1679 led to identifying the Apache "SetInputFilter DEFLATE" directive as a problem with implementing compression.
Apr 11 2020
"FutureGraph" is dead. Long live "HardpointEngine".
Apr 10 2020
Generators can't "return" until PHP 7:
Apr 9 2020
PHP has a setting called post_max_size. If a POST request is larger than this size, PHP does not populate $_POST or $_FILES.
Apr 8 2020
Apr 5 2020
Apr 3 2020
XHPAST currently can't build an AST for $result = yield ..., even though this is a valid construct. This is probably a straightforward fix.
Apr 1 2020
Feb 28 2020
I have some code which runs and looks plausible (i.e., not covered in piles of callback garbage), at least:
Feb 27 2020
Here's an actual example of loadHardpoints($objects, $hardpoint):
In the specific case of the Hardpoints, we currently often have code which loads objects but doesn't do anything with them. For example, most Query classes use didFilterResults() to fill things-that-sure-look-like-hardpoints, but few do anything with the results.