You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Abhishek Dasgupta (JIRA)" <ji...@apache.org> on 2016/07/30 11:04:20 UTC
[jira] [Commented] (MESOS-5790) Ensure all examples in Scheduler
HTTP API docs are valid JSON
[ https://issues.apache.org/jira/browse/MESOS-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400632#comment-15400632 ]
Abhishek Dasgupta commented on MESOS-5790:
------------------------------------------
RR: https://reviews.apache.org/r/50626/
> Ensure all examples in Scheduler HTTP API docs are valid JSON
> -------------------------------------------------------------
>
> Key: MESOS-5790
> URL: https://issues.apache.org/jira/browse/MESOS-5790
> Project: Mesos
> Issue Type: Improvement
> Reporter: Anand Mazumdar
> Assignee: Abhishek Dasgupta
> Labels: mesosphere, newbie
>
> Currently, there are a lot of JSON snippets in the [API Docs | http://mesos.apache.org/documentation/latest/scheduler-http-api/ ] that are not valid JSON i.e. have {{...}} to make the snippet succinct/easy to read. e.g.,
> {code}
> {{"filters" : {...}
> {code}
> However, this is a problem for framework developers who are trying to use the new API. Looking at the corresponding protobuf definitions can be a good place to start but hardly ideal.
> It would be good to address the shortcomings and make the JSON snippets complete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)