[allura:tickets] #7292 User profile API

[Igor Bondarenko <je...@users.sf.net>]

- **status**: in-progress --> code-review
- **Comment**:

Closed #568. `je/42cc_7292`



---

** [tickets:#7292] User profile API**

**Status:** code-review
**Milestone:** forge-backlog
**Labels:** 42cc 
**Created:** Tue Mar 25, 2014 09:29 PM UTC by Dave Brondsema
**Last Updated:** Wed Mar 26, 2014 09:15 PM 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 dev@allura.apache.org 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.