Moshi doesn't have naming policies for field name ...

# android

[gildor]

Moshi doesn't have naming policies for field name and it's big blocker for me. I don't want to refactor dozens and hundreds of network models. I know that this is intentionally, I read article by Jesse Wilson with rationale and I can agree with this position from abstract point of view. But practically such approach still looks not so good for me, especially when you have a few different APIs and I don't really like to violate Kotlin/Java naming policy for that (and also pollute your public API in some cases), so the only option to use annotation with Json field name, but data class become unnecessary wordy and it's error prone.
I understand, that probably you can write some adapter for that, but it's not the thing that I would to do right after move to a new json mapper