Hi Dave I did the permission check modification. Btw Now I came with a general solution for all modules including threads using same single js code without putting inside loops.
Here is the way. Each markdown_content we wrap with `class="active-md" data-markdownlink=""` data-markdownlink has ajax endpoint for checklist js snippet. So for main modules's value of data-markdownlink is "" so it will call .../update_markdown ../get_markdown etc. But for the threads it's different we need to add `value.url()` to get corrent endpoint so for those it will call relevant urls such as /p/allura/discussion/general/thread/86d45b7f/4194/update_markdown Please check latest commit diff and review this approach https://forge-allura.apache.org/u/shalithasuranga/allura/ci/test/ If it looks good we can easiliy add for all modules. we just need to add `get_markdown` and `update_markdown` with relevant permissions and also just need to add js code as extra js snippet Thanks --- ** [tickets:#8230] Make checklists interactive** **Status:** open **Milestone:** unreleased **Created:** Mon Sep 17, 2018 08:59 PM UTC by Dave Brondsema **Last Updated:** Fri Oct 05, 2018 04:28 AM UTC **Owner:** nobody It would be nice if the new checklists from [#8085] were interactive too for people that have edit access. The markdown-checklist package has some helper JS for it, but would take custom code to handle the ajax and do the update. Maybe use existing rest APIs for some artifact types, but everything (wiki page, ticket, blog post, comment, etc) will need to be handled specifically to hit the right endpoint and with the right data format. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
