Tom Wright
Tom Wright
On a side note, I do agree that more docs on exactly how different formats are interpreted would be helpful.
For that you can use the [keys and indexes selector](https://daseldocs.tomwright.me/selectors/keys-and-indexes). ```bash dasel -f file.toml -m '.-' STUFF MORESTUFF ``` Or if you wanted to select just the data without knowing...
This seems reasonable. I'll do some digging into the XML parser used and see if something is easily achievable.
This is an interesting use-case. Note to myself - This could be achieved with the `--format` flag if the selector was made available in the format templates here: https://github.com/TomWright/dasel/blob/b779b8820ed2b3f4c2d1adb5c0f299dccb785868/output_formatter.go#L63
This is a bit of an issue with the way that dasel accesses data. Dasel will: 1. Decode the XML data into raw data (maps, slices, primitives) 2. Process queries...
This is definitely an option. I'll take a look at sprig and see if I can include it in the next release.
I've added this in https://github.com/TomWright/dasel/commit/b779b8820ed2b3f4c2d1adb5c0f299dccb785868 and it will be included in the next release.
I will do once I prepare the release On Thu, 6 Jan 2022, 16:05 Kroum Tzanev, ***@***.***> wrote: > @TomWright thanks for considering this > request. May you could document...
I definitely want to support this. I'll be looking at supporting this in future releases.
I've just seen this - I agree that this could be very useful. I'd be happy to support this in the future.