Mike Farah
Mike Farah
Hmm - only problem with the way you're processing explode is that they key order is mangled if merge is processed first :/ Not a massive issues I guess...though I...
Yeah, I brought those changes back in to ensure the correct map key order. Afaik I included all the tests you added; so there's shouldn't be any gaps :/ -...
Fixed in v4.48.1
Will fix in the next release, this is the same issue as #2383; #2384
Fixed in https://github.com/mikefarah/yq/releases/tag/v4.46.1
Fixed in [v4.47.1](https://github.com/mikefarah/yq/releases/tag/v4.47.1) ; note that this requires the `--yaml-fix-merge-anchor-to-spec` flag to be set
Adding a `in` operator makes sense to me as well. Note that `jq` defines is as the inverse of `has` not `contains` (which is a little looser) - yq should...
There's logic in there already to only show it once - how are you getting it to show multiple times like that?
I'll be defaulting that flag to true (after the Xmas break), as the old behavior isn't correct - to remove the warning you could also set that flag to true...
Easiest way to do that is to format the variable string as valid yaml: ``` meh=[foo,bar,baz] ./yq -n '.catpants = env(meh)' catpants: [foo, bar, baz] ```