http://localhost/ticket/2698 <p> for description / other fields with markdown support </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/2698 Trac 0.12.3 toby Fri, 27 Jul 2012 08:39:38 GMT http://localhost/ticket/2698#comment:1 http://localhost/ticket/2698#comment:1 <p> I think this would be really helpful/nice </p> Ticket aron.carroll Thu, 02 Aug 2012 13:38:08 GMT http://localhost/ticket/2698#comment:2 http://localhost/ticket/2698#comment:2 <ul> <li><strong>owner</strong> changed from <em>aron.carroll</em> to <em>toby</em> </li> <li><strong>status</strong> changed from <em>new</em> to <em>assigned</em> </li> </ul> <p> We need an api endpoint that can render a markdown string on submission. </p> <ul><li>Client posts a string of text to the endpoint. </li><li>Server responds with a 200, text/html response containing the rendered markdown. </li><li>Server returns a 400 and empty body if the content is not valid markdown. </li><li>Server returns a 500 and empty body if something else crashes. </li></ul><p> Alternatively for better error handling we could use a JSON transport. </p> <ul><li>Client posts a blob of json containing a "content" key with the markdown string. </li><li>Server returns a 200 (application/json) and blob of json with a "content" key with the rendered markdown. </li><li>Server returns a 400 (application/json) and blob of json with a "error" key containing a useful message for the user. </li><li>Server returns a 500 (application/json) and blob of json with a "error" key containing a useful message for the user. </li></ul> Ticket toby Thu, 09 Aug 2012 20:14:12 GMT http://localhost/ticket/2698#comment:3 http://localhost/ticket/2698#comment:3 <ul> <li><strong>milestone</strong> changed from <em>demo phase 5</em> to <em>demo phase 4</em> </li> </ul> Ticket