#5650 Implement API endpoint for discussion tool
closed
nobody
General
2015-08-20
2013-01-22
No
[forge:site-support:#2464]
In particular, a user is requesting to make it easier to fix migrated posts that are improperly formatted due to markdown (he upgraded before we made the change to essentially disable markdown at upgrade time). But, I can see this as being something folks would want anyway.
Let's start with a readonly API. After that's working real well, we can figure out the details for posting changes back to a discussion.
The
RootRestControllerinForgeTrackerneeds an index method that displays roughly the same data as the index view of the discussion tool but in JSON (e.g. forum names, descriptions, last post, total). Then /p/myproject/discussion/myforum/ should list a particular forum's topics and any metadata already available (don't query too much for each topic, would make it slow). Then each topic thread should have an API too. Take advantage of the existing "_thread" API endpoint, it may accomplish some of the API needs for you. The ticket API uses it e.g. https://sourceforge.net/rest/p/allura/tickets/6046/ has adiscussion_thread_urlattribute and that has all the dicussion details. Include pagination on all these endpoints (see ForgeTracker API for reference). Make sure there's security checks so private tools or forums aren't shown.Created #323: [#5650] Implement API endpoint for discussion tool (4cp)
Related
Tickets:
#5650Closed #323.
je/42cc_5650