The API design takes more consideration, as we need to ensure that what we
add is going to be performant, consistent with the rest of the API, and
future-proof. Rendering additional data on a page can be done without
having to as closely consider future design changes, as it's not an an
interface t
Done. https://code.google.com/p/reviewboard/issues/detail?id=3700
Hopefully you can find some bandwidth internally or with a student for this
request. Considering you're going to add the info in a tab in the UI I
would hope exposing the same info via an API would be trivial.
Thanks,
EB
On Wedn
Evan,
It would be nice to have, but short of a third-party contribution to do it,
we probably don't have time. We might assign it as a student project for
one of the classes we work with. Mind filing an enhancement request?
-David
On Wed, Dec 17, 2014 at 5:41 PM, Evan Borgstrom
wrote:
>
> Thank
Thanks for the reply, David.
Will the data used in /users// be available via an API point as
well? I'm really looking to get this data programatically.
LMK.
Thanks,
EB
On Wednesday, December 17, 2014 4:18:10 PM UTC-8, David Trowbridge wrote:
>
> Evan,
>
> In Review Board 2.1, there will be a n
Evan,
In Review Board 2.1, there will be a new tab on the user page
(/users//) that lists each of the code reviews that they did. In
the meantime, the only other way to get this information would be to query
the database (either through the database directly, via the python shell,
or by writing an
