[BUG] Multi-word configuration properties for match queries don't work about kt-search

[jillesvangurp]

I agree, this is the better fix. I changed this because I see uses for JsonDsl beyond the search client. But it is a bit error prone to deal with so I'm fixing this properly with a separate pull request.

[jillesvangurp]

right, I'll have a look at that one. Thanks for reporting

[jillesvangurp]

Wow, this was broken in a lot of places. I changed the naming convention to default to asIs at some point without realizing I had to fix this all over the DSL. Fixed by #28

[yassenb]

Thanks but why was the default switched to "asIs"? Look at the many places where you need to override it and potential future extensions will have to be careful to override as well. Why not default to snake case when this is the default for OpenSearch/ElasticSearch?