Service fetch automatically changes snake_case to camelCase

[LaurensBurger]

Product versie / Product version

3.0.2

Customer reference

DH

Omschrijf het probleem / Describe the bug

Example HTTP query string with a "data_attrs" key:

{"type": ["https://objecttypen.nl/api/v2/objecttypes/23fb3e3e-c313-4be0-b8ed-51cdc5e31449"], "data_attrs": ["training__naam__exact__{{keuzeTraining}},training__status__exact__OPEN_VOOR_INSCHRIJVINGEN"]}

turns into "dataAttrs":

Which breaks the service fetch, until the form builder manually changes the camelCase back to snake_case.

This causes double actions to be performed after each migration of a form: first set the right service, then change the key's to whatever they need to be.

(It is also believed these changes get reverted in some scenario's and break the service fetch, because it's using "dataAttrs" again)

Verwacht gedrag / Expected behavior

The config that exists in the service fetch should not "change" under any circumstance.

Screen resolution

None

Device

None

OS

None

Browser

No response

[joeribekker]

Refinement: DRF camelcase might be the problem, maybe replace or work around (with a mechanism that is already there)?
Estimate: a day