Page MenuHomePhabricator

Fix an issue with user.whoami
ClosedPublic

Authored by epriestley on May 14 2015, 10:49 PM.
Tags
None
Referenced Files
F14060133: D12848.id30914.diff
Sun, Nov 17, 11:32 PM
F14059979: D12848.id30914.diff
Sun, Nov 17, 10:48 PM
F14053489: D12848.diff
Fri, Nov 15, 4:36 PM
F14050558: D12848.diff
Thu, Nov 14, 7:15 PM
F14042517: D12848.diff
Tue, Nov 12, 4:03 AM
F14028512: D12848.diff
Fri, Nov 8, 1:51 PM
F13984994: D12848.diff
Sun, Oct 20, 5:25 PM
F13982006: D12848.id30914.diff
Oct 19 2024, 8:41 PM
Subscribers

Details

Summary

Both user.whoami and user.query call the same wire formatting code, but expect different data.

Don't try to add availability data to user.whoami.

Stop adding email data to user.query. We've added it since D11791, but my intent was for it to be exposed only via user.whoami (i.e., expose your address, not others').

Test Plan
  • Called both methods.
  • Saw emails on user.whoami.
  • Saw availability on user.query.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Fix an issue with user.whoami.
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.May 14 2015, 11:44 PM
This revision was automatically updated to reflect the committed changes.