JsonCodable macro field names about sdk HOT 3 OPEN

Yes, it lacks any configurability at all right now. This is because the metadata introspection APIs for macros are not yet implemented (and we are hashing out the details still).

Once it is well supported, we will certainly add this feature (as well as some other configuration options).

from sdk.

There is a solution for this when all your data model's keys follow the same naming convention, which is creating a build.yaml folder in the root of your project.

targets:
  $default:
    builders:
      json_serializable:
        options:
          field_rename: snake

It also would be nice if we could configure each model's keys naming convention separately.

from sdk.

@FarisArmoush this issue is about the JsonCodable macro, which is different from the JsonSerializable builder (which is a code generator based on build_runner, not a macro).

from sdk.