Re: Issue 1133 in reviewboard: API to obtain the logged in user's name.
Updates: Status: Fixed Comment #7 on issue 1133 by chipx86: API to obtain the logged in user's name. http://code.google.com/p/reviewboard/issues/detail?id=1133 Added a new /api/session/ resource, which points to the logged in user. Committed to master (66b2f8c) -- You received this message because you are subscribed to the Google Groups "reviewboard-issues" group. To post to this group, send email to reviewboard-iss...@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 1133 in reviewboard: API to obtain the logged in user's name.
Comment #6 on issue 1133 by diwakergupta: API to obtain the logged in user's name. http://code.google.com/p/reviewboard/issues/detail?id=1133 I'd be perfectly happy with this approach. In fact, in my original request I said: "I went through the JSON API but I'm at a loss to find a call that either gives me all the review requests for the logged in user, or some easy way to obtain the username of the logged in user first and then use that to get the list of review requests." So yes, a way to get at the user name would be perfect! -- You received this message because you are subscribed to the Google Groups "reviewboard-issues" group. To post to this group, send email to reviewboard-iss...@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 1133 in reviewboard: API to obtain the logged in user's name.
Updates: Summary: API to obtain the logged in user's name. Status: Confirmed Comment #5 on issue 1133 by chipx86: API to obtain the logged in user's name. http://code.google.com/p/reviewboard/issues/detail?id=1133 There likely won't be any resource path for "The logged in user's ". Instead, what I want to do is make it easier to find out the logged in user, and use that for paths, so that we don't end up duplicating all the resources out there. Otherwise, we'll get requests for the logged in user's: * review requests * reviews * comments * watched groups * watched review requests * profile information etc That's just a lot of extra stuff to maintain, and I don't want to go that route. I'll repurpose this bug to make sure we add something for finding out the logged in user's name and information. Perhaps even linking to prebuilt queries for things like the review requests. -- You received this message because you are subscribed to the Google Groups "reviewboard-issues" group. To post to this group, send email to reviewboard-iss...@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.