Thanks for this excellent site, it's really useful!

I often come here when I'm stuck on something. At those times I always have to find the manual, too:

https://stedolan.github.io/jq/manual/

(Searching jq in a search engine is annoyingly difficult because it always thinks you mean jQuery!)

It would be super helpful if your jqplay site (which always comes up easily in a search) includ

People have to scroll too much on the GitHub page to even get to the README

Error

IOptions type is missing attribute "input" and therefor it can't be specified without errors. Workaround for now is to cast it as any. The fix should be pretty easy by simply adding input to the IOptions interface and adding the allowed types as "json", "file" or similar.

Environment

node v13.11.0
npmv 6.13.7

If so, let's see some ideas :)

The XML encoding in JSON used by oq (described here, it should have a name) does not preserve element order in mixed-content XML elements -- therefore oq only supports a subset of XML. This makes sense for most applications where XML is used in a similar way like JSON and YAML. Full support of XML (minus less used featur

Since the beginig of the times this project's name has been "Portainer Stack Utils", which describes what it is and what it does. In order to avoid possible future legal issues with Portainer registered trademark it should be renamed to something that does not include "Portainer". Also, it has evolved to include more than just "stacks", so the name should not limit to "Stack Utils". Whatever name

The instructions for the "objects" lesson always show what followsjq enclosed in single quotes, e.g. the '[.foo]' in the first example:

$ echo '{"foo": { "bar": "a value" }}' \
      | jq '[.foo]'

In the interactive tutorial, following suit with single quotes succeeds in the first two exercises:

Given:    'product' (type "data?" to view)
Challenge: Create a new object con