JSON. Do you know what it is? Are you familiarized with JSON? If you are not, please check some of this links
TheEye expected JSON as output of tasks scripts. At this moment, JSON is the only supported format as input of our API. Also we use JSON to encode every environment variables, even strings, that will be available within scripts.
We use JSON to keep every output and environment variable consistent between each other and with the same encoding. This will make it easy to parse and transfer data, and eventually automate the extraction and storage of the data.
The exception is when passing values from one task to another. In this case we try to convert values from JSON to string before using them as arguments.
Every string, in JSON format, is surrounded by doble quotes. So when a var is only a string, you will have to decode it first or, in other words, remove doble quotes.
After doing that, you will get the real value and will be ready to use.
JSON language support and processors
Almost every modern programming language has tools to encode/decode JSON and convert it into usable structures by the language.
|Language||Tool||Sample and Links|
|Unix bash/shell||jq||JQ Github|
|Windows cmd/bat||powershell||Microsoft Docs|
|PHP||json_encode / json_decode||PHP.net Manual|
|Python||json lib||Python Docs|
Reserved characters. Escape/Unescape
Some characters are reserved in JSON and must be properly escaped to be used in strings. Unproperly escaped strings could prevent the data to be correctly parsed generating errors.
List of special characters in JSON
|Backspace (ascii code 08)||\b|
|Form feed (ascii code 0C)||\f|
|Unicode hex||\u followed by four-hex-digits|