The 'cat << EOF' produces wrong output when using escaped quotes

[ninlil]

• Task version: v3.35.1
• Operating system: Ubuntu 20.04
• Experiments enabled: none

Basic shell command works exactly the same in sh, bash and zsh (i.e producing the exact same output as input)

$ cat << EOF
{
  "key1": "a simple text with an escaped doublequote \" in the text"
}
EOF
{
  "key1": "a simple text with an escaped doublequote \" in the text"
}

but the following task prints different outputs:

version: '3'
tasks:
  test:
    vars:
      TEXT: |
        {
          "key1": "a simple text with an escaped doublequote \" in the text"
        }
    cmds:
      - echo '{{.TEXT}}'
      - |
        cat << EOF
        {{.TEXT}}
        EOF

Output: (do note the last entry not having an escaped doublequote)

$ task test
task: [test] echo '{
  "key1": "a simple text with an escaped doublequote \" in the text"
}
'
{
  "key1": "a simple text with an escaped doublequote \" in the text"
}

task: [test] cat << EOF
{
  "key1": "a simple text with an escaped doublequote \" in the text"
}

EOF

{
  "key1": "a simple text with an escaped doublequote " in the text"
}

I see this as 1 bug and 1 feature-request:

feature suggestion: apart of settings your command using the "sh:" key, add a "stdin" or "input" key to be a variable

    cmds:
      - sh: cat
        stdin: TEXT

[mochja]

@ninlil this indeed seems to be a bug in the upstream gosh project. I am going to open a bug report there.

gosh
$ cat << EOF
> test \" test
> EOF
test " test

bash
bash-3.2$ cat << EOF
> test \" test
> EOF
test \" test
bash-3.2$

You can workaround the issue using here-string cat <<< {{.TEXT | shellQuote}}, which produce:

task: [test] cat <<< $'{\n  "key1": "a simple text with an escaped doublequote \\" in the text"\n}\n'
{
  "key1": "a simple text with an escaped doublequote \" in the text"
}

[mvdan]

FWIW this bug was fixed upstream back in February.