Best way to handle camelCase properties when calling ->all() on Data class?

[pejeio]

Hi everyone,

I have the following Data class:

use App\Models\Car;
use App\Models\City;
use Spatie\LaravelData\Attributes\MapName;
use Spatie\LaravelData\Attributes\Validation\Exists;
use Spatie\LaravelData\Data;
use Spatie\TypeScriptTransformer\Attributes\Optional as TypeScriptOptional;
use Spatie\TypeScriptTransformer\Attributes\TypeScript;

#[TypeScript()]
class NewCarPayloadData extends Data
{
    public function __construct(
        #[Exists(Car::class, 'id')]
        public int $carId,
        #[Exists(City::class, 'id')]
        public int $pickupCityId,
        #[TypeScriptOptional]
        public ?string $deadline,
        #[TypeScriptOptional]
        public array $features
    ) {}
}

In my controller I have:

public function store(NewCarPayloadData $data)
{
    Car::create($data->all());
    return redirect()->route('home');
}

Here, $data->all() gives me camelCase keys like carId, which don’t match the snake_case column names in the database. So this fails.

The only workaround I see is manually mapping everything:

Car::create([
    'car_id' => $data->carId,
    'pickup_city_id' => $data->pickupCityId,
    'deadline' => $data->deadline,
    'features' => $data->features,
]);

…but that defeats the elegance of the DTO, especially if the model has many fields.

I also experimented with SnakeCaseMapper in #[MapInputName] and #[MapOutputName], but none of those gave me the result I expected either.

Is there a recommended way to handle this? Ideally, I’d like to keep using camelCase on the frontend and in TypeScript, but snake_case in the DB without this extra mapping.

Thanks in advance!