Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optionally use interfaces in entities and DTOs #4

Open
kzfabi opened this issue Aug 28, 2015 · 2 comments
Open

Optionally use interfaces in entities and DTOs #4

kzfabi opened this issue Aug 28, 2015 · 2 comments

Comments

@kzfabi
Copy link
Owner

kzfabi commented Aug 28, 2015

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

@kzfabi
Copy link
Owner Author

kzfabi commented Aug 28, 2015

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.

@kzfabi
Copy link
Owner Author

kzfabi commented Aug 28, 2015

VinceI wrote Jul 19, 2013 at 1: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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant