Currently, the generated class name is always the same as the table name.
In my project, I maintain a clear separation between domain entities and database records (using a Record suffix). It would be very helpful to have the ability to define custom class naming rules for generated models. For example:
- Specify a prefix/suffix via YAML configuration.
- Or provide an annotation on the table definition (similar to how an output parameter works in query annotations).
This would make it easier to integrate the generated models into Clean Architecture or DDD-style projects.
Currently, the generated class name is always the same as the table name.
In my project, I maintain a clear separation between domain entities and database records (using a
Recordsuffix). It would be very helpful to have the ability to define custom class naming rules for generated models. For example:This would make it easier to integrate the generated models into Clean Architecture or DDD-style projects.