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/
Another important thing I forgot to mention is the list of projects that a user is a member of. Including their role in the project (admin, developer) would be good too.
Closed #568.
je/42cc_7292
Merged, with a few tweaks:
__json__
) would actually persist to the databaseRelated
Tickets:
#7292