Tom Wright

I would yes, it might take a little work though since I current have no Windows runners on the pipeline. I'm open to PR's if you've done this workflow before...

I am currently reworking the encode/decode logic for all formats as part of https://github.com/TomWright/dasel/pull/289. I can reevaluate and hopefully fix this issue as part of that work.

Thank you for the detailed examples @piotrwiniarczyk-silvair. I will take a look at these cases to fully understand them ASAP.

Hey @piotrwiniarczyk-silvair , I have fixed this issue. To access the fix immediately please use the development version of dasel. The fix will be included in the next release.

This has been released under `v2.4.0`.

Sorry I forgot about XML - my mistake. I will revisit that.

Dasel uses the following package for yaml parsing: https://github.com/go-yaml/yaml I can do some digging to see if there is a workaround for this.

I believe I have fixed this here: https://github.com/TomWright/dasel/pull/289 The PR is still a WIP but a fix should be coming soon.

It looks like the issue is still present.

On the surface this looks good, but we'll run into trouble when we use formats other than JSON... CSV for example. I'll have a think about how this can be...