2
Vote

[Feature] Optionally use interfaces in entities and DTOs

description

As a developer I would like to have my entities and DTOs implement a common interface (one for entities and one for DTOs) so that I can code common operations targeting generic entities and generic DTOs.

Notes

comments

ffernandez wrote Jul 11, 2013 at 5:17 AM

Define parent as abstract or concrete class instead of interface so we can include properties in the parent that don't need to be implemented by the children (DTOs). Let the user choose the parent name.

Include a panel where the user can add/remove properties to the parent indicating name and type. For the type allow to input FQN so the user can use his own types, Built-In Data Types, other framework types, etc. Indicate if type is nullable.

Let the user choose his own parent type using a FQN instead of one generated by the tool.

VinceI wrote Jul 19, 2013 at 4:15 AM

This feature could be as simple as allowing a user to specify a Base Class (e.g., "BaseDTO") that the user can then implement after the generation of the DTOs.