Tom Wright

I believe I've fixed this issue here: https://github.com/TomWright/dasel/commit/7e2937e42fffe24291114d91c81f421b0f4f1caf It's not yet merged as it's part of a bigger encoding/decoding change.

@rhtenhove This is pretty convoluted but does what you need. I do want to include some functionality to simplify this a lot. ``` orDefault(plugins.all().filter(equal(type(),array)).all().filter(equal(type(),object)).assets?.all().filter(equal(.,README.md)).count(),0).moreThan(.,0) ``` Essentially filter out any non...

The method of validation dasel uses here is just to attempt to read the YAML and fail if it cannot be parsed, so largely the same approach kubernetes is using....

Yes of course. It may be good to hide it behind a `--strict` flag so it doesn't catch other users off-guard

I agree that option 1 is probably the right way to go here. 1. It allows us to instantiate a parser based on some options given to the factory method....

This is reasonable. The index current index operator has a syntax of: ``` index(0) index(0,1,2) [0] [0,1,2]

We can do something similar. It'll be a little more long form because the join func doesn't have shorthand right now, but something like: ``` dasel -r json `join(province[2:],city[2:])` ```

In my work on ordered maps I am writing custom logic around yaml encoding/decoding. I expect I'll be able to resolve this issue when reading but writing could result in...

Perhaps behind a flag. I don't want people to accidentally remove all aliases from their files

The trouble comes because dasel decodes all input data into a generic format, before processing the data and encoding back into the desired format. This is how the cross-format transformations...