{"id":544,"date":"2018-01-07T15:00:36","date_gmt":"2018-01-07T14:00:36","guid":{"rendered":"http:\/\/xml-buddy.com\/xmltribune\/?p=544"},"modified":"2018-01-07T15:08:31","modified_gmt":"2018-01-07T14:08:31","slug":"editor-layout-for-json-schema-files","status":"publish","type":"post","link":"https:\/\/www.xml-buddy.com\/xmltribune\/editor-layout-for-json-schema-files\/","title":{"rendered":"My editor layout for working with JSON schema files"},"content":{"rendered":"<p>JSONBuddy offers a lot of functionality while you are editing a JSON schema file. It is even not always easy to have all of the information visible on the screen. So here is the editor layout\u00a0I am using whenever I have a JSON schema file open in JSONBuddy:<\/p>\n<div id=\"attachment_546\" style=\"width: 1608px\" class=\"wp-caption aligncenter\"><a href=\"http:\/\/xml-buddy.com\/xmltribune\/wp-content\/uploads\/2018\/01\/json-buddy-schema-editor-layout-e1515332523640.png\"><img aria-describedby=\"caption-attachment-546\" loading=\"lazy\" class=\"size-full wp-image-546\" src=\"http:\/\/xml-buddy.com\/xmltribune\/wp-content\/uploads\/2018\/01\/json-buddy-schema-editor-layout-e1515332523640.png\" alt=\"Editor layout for working with JSON schema documents\" width=\"1598\" height=\"945\" srcset=\"https:\/\/www.xml-buddy.com\/xmltribune\/wp-content\/uploads\/2018\/01\/json-buddy-schema-editor-layout-e1515332523640.png 1598w, https:\/\/www.xml-buddy.com\/xmltribune\/wp-content\/uploads\/2018\/01\/json-buddy-schema-editor-layout-e1515332523640-300x177.png 300w, https:\/\/www.xml-buddy.com\/xmltribune\/wp-content\/uploads\/2018\/01\/json-buddy-schema-editor-layout-e1515332523640-768x454.png 768w, https:\/\/www.xml-buddy.com\/xmltribune\/wp-content\/uploads\/2018\/01\/json-buddy-schema-editor-layout-e1515332523640-1024x606.png 1024w, https:\/\/www.xml-buddy.com\/xmltribune\/wp-content\/uploads\/2018\/01\/json-buddy-schema-editor-layout-e1515332523640-624x369.png 624w\" sizes=\"(max-width: 1598px) 100vw, 1598px\" \/><\/a><p id=\"caption-attachment-546\" class=\"wp-caption-text\">Editor layout for working with JSON schema documents<\/p><\/div>\n<p>This way I have a lot of entry helpers and additional information about the current JSON schema quickly available:<\/p>\n<ol>\n<li>The <strong>generated sample data<\/strong> to get an idea what kind of JSON is valid against the schema and to easily generate a new JSON instance (using the &#8220;JSON | Generate sample document from JSON schema&#8221; command).<\/li>\n<li>The <strong>list of schema keywords<\/strong> is just below.<\/li>\n<li>You get a list of messages on the bottom at the left-hand side. The built-in <strong>JSON schema analyzer<\/strong>\u00a0(available soon) is always working in the background and reports all issues about the current schema. For example, unknown type specifiers and references which can&#8217;t be resolved.<\/li>\n<li>And finally the text of the <strong>JSON schema specification<\/strong> of the currently selected schema keyword to the right.<\/li>\n<\/ol>\n<p>All of this is available in JSONBuddy to support the creation and editing of JSON schema documents in less time.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>JSONBuddy offers a lot of functionality while you are editing a JSON schema file. It is even not always easy to have all of the information visible on the screen. So here is the editor layout\u00a0I am using whenever I have a JSON schema file open in JSONBuddy: This way I have a lot of entry helpers and additional information&#8230; <a href=\"https:\/\/www.xml-buddy.com\/xmltribune\/editor-layout-for-json-schema-files\/\">Read more &raquo;<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_mi_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0},"categories":[4],"tags":[23,67,40],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.xml-buddy.com\/xmltribune\/wp-json\/wp\/v2\/posts\/544"}],"collection":[{"href":"https:\/\/www.xml-buddy.com\/xmltribune\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.xml-buddy.com\/xmltribune\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.xml-buddy.com\/xmltribune\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.xml-buddy.com\/xmltribune\/wp-json\/wp\/v2\/comments?post=544"}],"version-history":[{"count":3,"href":"https:\/\/www.xml-buddy.com\/xmltribune\/wp-json\/wp\/v2\/posts\/544\/revisions"}],"predecessor-version":[{"id":549,"href":"https:\/\/www.xml-buddy.com\/xmltribune\/wp-json\/wp\/v2\/posts\/544\/revisions\/549"}],"wp:attachment":[{"href":"https:\/\/www.xml-buddy.com\/xmltribune\/wp-json\/wp\/v2\/media?parent=544"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.xml-buddy.com\/xmltribune\/wp-json\/wp\/v2\/categories?post=544"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.xml-buddy.com\/xmltribune\/wp-json\/wp\/v2\/tags?post=544"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}