--explodeAnchors / -X doesn't explode keys (work in 3.3.1 and 3.3.2)

[OnkelTem]

Describe the bug

-X / --explodeAnchors doesn't work now in 3.3.2 or 3.3.1 (for the read command at least).
The last version when it worked was 3.3.0.

This should work:

1.yaml

errors:
  - &ts_sync_loss ts_sync_loss
properties:
  *ts_sync_loss: int

but outputs:

errors:
  - ts_sync_loss
properties:
  *ts_sync_loss: int

i.e. ts_sync_loss is not dereferenced .

Command

$ <1.yml yq r -X -

Version 3.3.0 does work right.

[mikefarah]

please follow the bug template - there is not enough information in this for me to replicate

[OnkelTem]

@mikefarah Mike, I updated the issue. Try it now please.

[mikefarah]

That's not how you use anchors and aliases, I can't quite work out what you are trying to do, but it needs to be something like:

errors:
  - &ts_sync_loss ts_sync_loss # this creates a variable for the value 'ts_sync_loss'
properties: *ts_sync_loss # this references that variable

[OnkelTem]

@mikefarah I don't think you're right.

You can try out my example with any of the available validators/parsers:
https://yaml-online-parser.appspot.com/
https://codebeautify.org/yaml-validator
http://www.yamllint.com/
—it works just fine, so I believe it's definitely a bug.

[OnkelTem]

Sorry, but we are you keeping this closed @mikefarah?

[OnkelTem]

Just to clarify things.

It transpired that the original YAML was actullay INCORRECT.

Specifically, this:

errors:
  - &ts_sync_loss ts_sync_loss
properties:
  *ts_sync_loss: int

should read as:

errors:
  - &ts_sync_loss ts_sync_loss
properties:
  *ts_sync_loss : int

(note the extra space after *ts_sync_loss).
Thus the reference PyYaml parser was actually wrong by allowing for space-less colons after anchors (but works well with the correct syntax).

Unfortunately for this tool it doesn't make any difference, it still fails.

Consider this YAML:

devs:
  - &dev1  Alice
  - &dev2  Bob
  - &devop Jane
time:
  - name: Project 1
    devs:
      *dev1 : 120 hours
      *devop : 32 hours 
  - name: Project 2
    devs:
      *dev2 : 154 hours
      *devop : 21 hours 

It works with these popular YAML parsers:

• PyYAML [Link to a demo]
• NPM js-yaml [Link to a demo]
• NPM yaml
• PHP's yaml_parse()

[mikefarah]

Ok I originally misunderstood the yaml file - now I see that the aliases are for the map keys! I didn't realise you could do that in yaml, neat.

Sorry it took me a while. This should be fixable.

[mikefarah]

Fixed in https://github.com/mikefarah/yq/releases/tag/3.4.0