- **status**: code-review --> closed - **QA**: Dave Brondsema - **Milestone**: forge-backlog --> forge-may-2 - **Comment**:
Merged, with a few tweaks: * 1b79f47 [#7292] add user full name; adjust profile_url field name * 1ed540f [#7292] for safety, don't return ming-instrumented objects since any modifications someone might do elsewhere (after calling `__json__`) would actually persist to the database * 1b51b77 [#7292] move UserProfileRestController from base rest.py file, to profile module * 6b9cea0 [#7292] don't need to list tools in profile API, already in user-project API * end-user API docs --- ** [tickets:#7292] User profile API** **Status:** closed **Milestone:** forge-may-2 **Labels:** 42cc **Created:** Tue Mar 25, 2014 09:29 PM UTC by Dave Brondsema **Last Updated:** Wed Apr 09, 2014 08:36 AM UTC **Owner:** nobody Create an api endpoint on the profile tool, so it'll be at /rest/u/USERNAME/profile/ which includes username, full name, date registered, and other fields on the profile webpage if they are set (e.g. location, timezone, gender, skills, website, etc). Maybe each `ProfileSectionBase` class could have its own `__json__` method and return its own data. Then the `[allura.user_profile.sections]` extension points control both the content of the profile webpage and profile API. Add a new field in the /rest/u/USERNAME/ endpoint that gives the full URL to the profile endpoint so that it is easily discovered. Provide some markdown to explain the API fields, that can be added to https://sourceforge.net/p/forge/documentation/Allura%20API/ --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
