#5650 Implement API endpoint for discussion tool

v1.0.0
closed
nobody
General
Cory Johns
2015-08-20
2013-01-22
Chris Tsai
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.

Related

Tickets: #5650
Tickets: #6424

Discussion

  • Dave Brondsema

    Dave Brondsema - 2013-04-22
    • labels: support, p3 --> support, p3, 42cc
    • Milestone: limbo --> forge-backlog
     
  • Dave Brondsema

    Dave Brondsema - 2013-04-22

    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 RootRestController in ForgeTracker needs 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 a discussion_thread_url attribute 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.

     
  • Igor Bondarenko

    Igor Bondarenko - 2013-04-23
    • status: open --> in-progress
     
  • Igor Bondarenko

    Igor Bondarenko - 2013-04-23

    Created #323: [#5650] Implement API endpoint for discussion tool (4cp)

     

    Related

    Tickets: #5650

  • Chris Tsai - 2013-04-26
    • labels: support, p3, 42cc --> support, p3, 42cc, allura-api
     
  • Igor Bondarenko

    Igor Bondarenko - 2013-05-07
    • status: in-progress --> code-review
     
  • Igor Bondarenko

    Igor Bondarenko - 2013-05-07

    Closed #323. je/42cc_5650

     
  • Cory Johns

    Cory Johns - 2013-06-18
    • QA: Cory Johns
     
  • Cory Johns

    Cory Johns - 2013-06-26
    • status: code-review --> closed
    • Milestone: forge-backlog --> forge-jun-28
     

Log in to post a comment.