I just noticed, when working on a Vue3 (Frontend Framework) project, which needs an JSON:API requests and therefore converters between Drupals snake_case field names and Vue3's expected camleCase names, that most camelCase to snake_case converters treat numbers in strings as something which needs to be separated by an "_". Therefore the conversion of "address_line1" to camelCase is fine "addressLine1" but the back convert is "address_line_1", which then gets errors thrown by JSON:API.
I guess there is no easy fix for that. I just wanted to mention it. because Decoupled frontends based on javascript will very likly have the same Javascript / Typescript naming conventions.
Fixed
1.12
Code
Thanks for reporting, but there's nothing we can do on our end.
Ideally your converter supports having a custom mapping for cases like this.
Automatically closed - issue fixed for 2 weeks with no activity.