Page MenuHomePhabricator

Align "RevisionQuery->needCommitPHIDs()" to use Edges, not the legacy table
ClosedPublic

Authored by epriestley on Apr 22 2019, 7:34 PM.
Tags
None
Referenced Files
F18672179: D20459.id48813.diff
Thu, Sep 25, 6:55 AM
F18657096: D20459.diff
Tue, Sep 23, 12:28 AM
F18610642: D20459.id.diff
Sun, Sep 14, 5:16 AM
F18610566: D20459.diff
Sun, Sep 14, 5:01 AM
F18569933: D20459.id48834.diff
Wed, Sep 10, 3:00 AM
F18569931: D20459.id48813.diff
Wed, Sep 10, 3:00 AM
F18519101: D20459.diff
Fri, Sep 5, 3:54 PM
F18154683: D20459.id48834.diff
Aug 14 2025, 8:26 PM
Subscribers
None

Details

Summary

Depends on D20458. Ref T13276. Although I'm not thrilled about "needCommitPHIDs()", it has a few callers, including custom fields. Allow "need + attach + get" to survive for now since they're reasonably modern, at least.

However, use edges instead of "TABLE_COMMIT" and require need...() + get...(), removing the direct load...().

Also remove RevisionQuery->withCommitPHIDs(...), which has no callers.

Test Plan
  • Grepped for loadCommitPHIDs (only two hits, the private RevisionQuery method).
  • Called "differential.getrevision", got commits.
  • Viewed a revision, saw "Commits: ...".
  • Grepped for withCommitPHIDs(), no callers on RevisionQuery (some other query classes have methods with this name).
  • Called "differential.query", got commits.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable