Tom Wright

I am in the middle of reworking the yaml processing dasel does. A good bunch of those issues are solved with the rework, and some of them just aren't yaml...

@electriquo If you have a look to the code I'd be more than happy to take a look

Honestly I'd forgotten about this, but thank you for the reminder. I'll see what I can do

I do have a WIP locally but found the decoder/encoder may need some restructuring. I'm more than happy to accept PR's on the subject. The code that needs to change...

Good question. Decoding only is a good first step. We'll need to handle the new node type within the decoder, but all of the values end up being written to...

As of `v2.8.0` dasel supports this feature when reading. Note that as of now, writes will de-reference the aliases. I'm releasing as-is to unblock read use-cases - these never worked...

I've had a look and this is a tough problem to solve. Related: https://github.com/golang/go/issues/51649 I'm going to do some thinking and come back to this.

Thanks for your patience on this. I believe I have resolved this issue, see: ``` $ echo '{"foo":null}' | ./dasel -r json { "foo": null } $ echo '{"foo":null}' |...

I'm not against this but I'd like to push further with features before I put work in here. I'm happy for contributions to enable these install methods though. As a...

Thanks for raising this issue. I am able to replicate it and will do some digging. As an FYI, you are able to create a complex object using any of...