Good point about existing fields. We can create new endpoints. They could be part of our official REST API. The `PATCH` http method (instead of PUT/POST) is a good one for just updating a single field. I don't think a single API endpoint for all types of artifacts would work, because each one (ticket, wiki page, comment, blog post, etc) has a different way of being identified/named and stores its markdown in different fields. So we would probably have to update many existing APIs that accept POST to accept PATCH too. And probably create a few APIs if they don't have one yet.
It sounds like quite a bit of work, but if you wanted to do it, I'd suggest starting with just one like a ticket. Then we could work through all the details of that before applying the pattern to all the other places. --- ** [tickets:#8230] Make checklists interactive** **Status:** open **Milestone:** unreleased **Created:** Mon Sep 17, 2018 08:59 PM UTC by Dave Brondsema **Last Updated:** Mon Oct 01, 2018 10:18 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.
