Tom Wright

@EzSoftware2015 @zhangshuyx Thanks for extra info here, that's very useful

Dasel does use a standard JSON encoder here so I'm happy as far as the encoding goes. An easy solution here would be to use the [format](https://daseldocs.tomwright.me/usage/flags/format) flag to be...

Hi @GDA92, @deus101, This is fixed in `v1.27.2` ```bash ~/repos/github.com/TomWright/dasel [master] $ dasel -v dasel version development-v1.27.2 ~/repos/github.com/TomWright/dasel [master] $ echo '{ "x": 123456.1, "y": 1234567.1 }' | dasel -r...

Sorry for the slow work here, I've been busy! This is fixed in `v1.27.3`.

> Note that `dasel --help` produces the following Usage section: > > ``` > Usage: > dasel select -f -p -s [flags] > ``` > > ... essentially implying there's...

Can I bump this to find out if it is an option? If not I'll work on my own solution

I would also appreciate this feature. I would like to parse ``` a=1 [section1] b=2 ``` Into ``` map[string]interface{}{ "a": 1, "section1": map[string]interface{}{ "b": 2, }, } ```

@unknwon I thought the original request was asking that we could decode into a generic map type. Sorry if I've misunderstood 🙂 If that is the case, do you know...

Yes it looks like that helps, thank you. I want to finish up the changes I'm making to the existing parsers and then I can add support for this

I am looking to resolve this issue as part of https://github.com/TomWright/dasel/pull/289.