jq sample(definition syntax for variable and function)

ques0942 — Mon, 01 Apr 2019 12:32:59 +0000

jq

use query string from a file

you can write query at a file like below.

curl "http://localhost:8080/" | jq -f jq_query

variable definition

echo '{"a": "valueA"}' |\
  jq '. | {"b": "valueB"} as $v | {"a2": .a, "b2": $v.b}'
# output
# {
#  "a2": "valueA",
#  "b2": "valueB"
#}

function definition and if statement

echo '[{"a": "valueA"}, {"b": "valueB"}]' |  jq '[.[] | 
    def replace(d): d as $d | 
      if (.a == null and .b != null) then {"a": $d.a, "b": .b}
      elif (.a != null and .b == null) then {"a": .a, "b": $d.b}
      elif (.a == null and .b == null) then {"a": $d.a, "b": $d.b}
      else {"a": .a, "b": .b}
      end;
    replace({"a": "valueA2", "b": "valueB2"})]'
# output
#[
#  {
#    "a": "valueA",
#    "b": "valueB2"
#  },
#  {
#    "a": "valueA2",
#    "b": "valueB"
#  }
#]

xerrors has less feature about trace's detail

ques0942 — Thu, 07 Mar 2019 13:48:33 +0000

This is feedback for Go 2 Proposal.
This is my opinion. if you has any opinions for proposals, please feedback your one.

The proposal of Go 2 Error Values is looks good to me. Inspection and printing feature is simple and ease to use. but not enough to read error stacktrace.
Some case(i faced when i used sentry), we want to read error stacktrace(ie. program counter, function name, line number...etc) to create structured error data. Implementation of this proposal("xerrors") provide Printer interface only which is used to print error.
This interface is focus on printing and formatting so we can't use it to read stacktrace. If i want to read stacktrace by using "xerrors", i must write dirty code.
If "xerrors" will reveals stacktrace or returns runtime.Frame, it will be very useful. so i support this idea.

DEV Community: ques0942

jq sample(definition syntax for variable and function)

jq

use query string from a file

variable definition

function definition and if statement

xerrors has less feature about trace's detail