Mike Farah

Hi - sorry I must have missed this! This is an issue with the underlying go-yaml parser - which I don't have control of unfortunately. I beleive there are issues...

In that case you will need to use a different string block indicator, have a look at that yaml multiline site, I think you need to use '|' ________________________________ From:...

Raised an issue here: https://github.com/go-yaml/yaml/issues/737

I'm not really sure what this means - however I don't want to put any specific YAML format support into `yq`. Is there is a generic way of supporting what...

Doh I should have picked that up - sorry, will fix.

On closer inspection, this is an issue with the underling go-yaml parser (https://github.com/go-yaml/yaml/issues/610, https://github.com/go-yaml/yaml/issues/695). "head2" is somehow being associated as the head comment of the key 'ab' and not the...

As a workaround/hack, you can recursively match the nodes that have the comments attached to them: ``` yq e '... | headComment | select(. != "")' examples/data1.yaml ``` ``` head1...

Yeah, though there hasn't been much action on that repo for a while :/ ________________________________ From: MisterMX ***@***.***> Sent: Tuesday, November 23, 2021 8:30:37 PM To: mikefarah/yq ***@***.***> Cc: Mike...

This is a problem with the underlying go-yaml parser - it's not very good at placing comments correctly :( Looks related to https://github.com/go-yaml/yaml/issues/695

Possibly https://github.com/go-yaml/yaml/issues/610