Hi Robert.
The document is already there. Please check
http://www.reviewboard.org/docs/manual/dev/webapi/2.0/resources/user/ under
Description.
Hongbin
On Sat, Sep 3, 2011 at 12:44 AM, Robert Munteanu
robert.munte...@gmail.comwrote:
Hi Christian,
I understand the reason behind this and I don't have a strong
preference either way. Perhaps the best solution would be to document
this feature in the RB API guide? That was my first step, before
mailing the group.
Robert
On Fri, Sep 2, 2011 at 9:24 PM, Christian Hammond chip...@chipx86.com
wrote:
Hi Robert,
I think the idea was that by hiding the fields themselves, it indicates
we
can't send that data, rather than them just being empty bits of data.
Being
explicit about needing to check that could be considered a good thing. On
the other hand, it does break backward-compatibility.
Christian
On Friday, September 2, 2011, Robert Munteanu robert.munte...@gmail.com
wrote:
Thanks for the reply, I now understand the root cause. As for my
point, it was that the actual JSON and XML field declarations should
still appear, i.e. instead of something like
user
id1/id
usernamebla/username
/user
there should be
user
id1/id
usernamebla/username
email/
/user
This would make sense from a consistency point of view and avoid
making special cases in code, for both JSON and XML parsers.
Robert
On Fri, Sep 2, 2011 at 4:53 PM, Hongbin Lu hongbin...@gmail.com
wrote:
Hi Robert.
I believe this is the private profile feature which was added in 1.6
RC1.
http://code.google.com/p/reviewboard/issues/detail?id=2127
In general, user profiles are private by default so that email,
first_name
and last_name won't show up. Maybe you can upgrade your account to site
admin if you can. Those fields should always show to site admin.
Hongbin
On Fri, Sep 2, 2011 at 2:41 AM, Robert Munteanu
robert.munte...@gmail.com
wrote:
Hi,
I am not sure whether this is a bug or not, but here goes:
The API does not return the {first_name, last_name, email} fields for
some
users ( 3 out of 8135 on reviews.review-board.org ) . I assume that
this
is
some sort of privacy setting, but I think it would be best for the
fields to
be returned but empty, as it makes consistent parsing easier.
This happens for both the JSON and the XML formats.
One such example is
http://reviews.reviewboard.org/api/users/mbait/
Let me know if I should open a bug report or if this is expected .
Robert
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
--
Sent from my (old) computer
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
--
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
--
Sent from my (old) computer
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
