Many JSON formats are completely brain dead. Instead of the natural { key : value }, these formats go “all meta’, using { Field: “name”, Value: “amateur” } or { “name” : “name”, “value”: “amateur” }. This “meta key-value” approach is a stupid format that doesn’t provide any extra extensibility, yet completely destroys the concept of a useful schema. <\/p>\n
This poor design also complicates json query<\/a> (jq<\/a>) (see cookbook<\/a> too)<\/p>\n The recipe to extract the value you want:<\/p>\n With this input file:<\/p>\n Many JSON formats are completely brain dead. Instead of the natural { key : value }, these formats go “all meta’, using { Field: “name”, Value: “amateur” } or { “name” : “name”, “value”: “amateur” }. This “meta key-value” approach … Continue reading $ jq -r '.[] | select( .Field == \"properties\").Value' output.json\nthis is a terrible design<\/pre>\n
$ cat output.json\n[\n {\n \"Field\": \"description\",\n \"Value\": \"human description of a terrible design\"\n },\n {\n \"Field\": \"enabled\",\n \"Value\": true\n },\n {\n \"Field\": \"id\",\n \"Value\": \"fa722ed8b4f56d14bcf77537\"\n },\n {\n \"Field\": \"name\",\n \"Value\": \"your-name\"\n },\n {\n \"Field\": \"properties\",\n \"Value\": \"this is a terrible design\"\n }\n]<\/pre>\n","protected":false},"excerpt":{"rendered":"