{"id":687,"date":"2026-03-05T21:35:44","date_gmt":"2026-03-05T21:35:44","guid":{"rendered":"https:\/\/camilo.matajira.com\/?p=687"},"modified":"2026-03-05T21:53:10","modified_gmt":"2026-03-05T21:53:10","slug":"jed-v0-4","status":"publish","type":"post","link":"https:\/\/camilo.matajira.com\/?p=687","title":{"rendered":"jed v0.5"},"content":{"rendered":"\n

Available: https:\/\/github.com\/camilomatajira\/jed<\/a><\/p>\n\n\n\n

In this release, the main objective was to allow filters to be applied at any depth of the JSON<\/strong>, without having to specify the full path from the root.<\/p>\n\n\n\n

Examples<\/h4>\n\n\n\n

In the following example, connectors.json<\/code> contains around 1800 objects<\/strong>.
We can print the first connector using the expression 0,0p<\/code>.<\/p>\n\n\n\n

0,0<\/code> is an Array Range<\/strong>, but how does it work if the key at the root is \"connectors\"<\/code> and not the array itself?<\/p>\n\n\n\n

This is precisely what this release enables. Even though the Array Range does not match the root (connectors<\/code>) (because it’s an object, and not an array), jed<\/code> continues trying to match it recursively<\/strong>.<\/p>\n\n\n\n

As a result, 0,0<\/code> can then be applied to the array under \"connectors\"<\/code>, and the filter is applied there.<\/p>\n\n\n\n

<\/circle><\/circle><\/circle><\/g><\/svg><\/span>