You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the time of the filing of this issue, Zed is at commit 4ffdf3e. This idea came up while the team was looking at the examples that motivated the opening of #4555 and #4565.
There's tons of tools out there that require JSON as input, and many Zed users still rely on those tools and may need to feed the output from their Zed queries into them. Since turning richer Zed values into JSON will likely "dumb down" many of the values (e.g., IP addresses become strings, sets become arrays, etc.) such users are likely to want to closely examine that JSON output while iterating on their Zed scripts so they know it will be a match for their downstream JSON tooling. Right now the easiest way to see that JSON output is to use the -j flag on zed or zq, which is ok, but if the user is working in Zui, now they either need to Export to JSON or jump to the shell to run zed on their lake behind Zui, which is less convenient. Therefore it might be handy to have an operator in Zed that effectively does all the same conversions that would happen with -j but still keep the values as Zed types in the pipeline. Now the user could see the would-be JSON output right in Zui, pretty-print it at the shell with -Z, do further processing in the pipeline knowing the values have been "reset" to JSON-level simplicity, etc.
The text was updated successfully, but these errors were encountered:
At the time of the filing of this issue, Zed is at commit 4ffdf3e. This idea came up while the team was looking at the examples that motivated the opening of #4555 and #4565.
There's tons of tools out there that require JSON as input, and many Zed users still rely on those tools and may need to feed the output from their Zed queries into them. Since turning richer Zed values into JSON will likely "dumb down" many of the values (e.g., IP addresses become strings, sets become arrays, etc.) such users are likely to want to closely examine that JSON output while iterating on their Zed scripts so they know it will be a match for their downstream JSON tooling. Right now the easiest way to see that JSON output is to use the
-j
flag onzed
orzq
, which is ok, but if the user is working in Zui, now they either need to Export to JSON or jump to the shell to runzed
on their lake behind Zui, which is less convenient. Therefore it might be handy to have an operator in Zed that effectively does all the same conversions that would happen with-j
but still keep the values as Zed types in the pipeline. Now the user could see the would-be JSON output right in Zui, pretty-print it at the shell with-Z
, do further processing in the pipeline knowing the values have been "reset" to JSON-level simplicity, etc.The text was updated successfully, but these errors were encountered: