Not sure if there is a better way to submit suggestions for improvements, as GitHub Issues are only for the non commercial version? Don't want a suggestion to lower our number of support tickets.
ABPSuite by default creates DTOs with different DTOs for each AGUD/CRUD operation. While this might be the most fancy solution, in many cases, just having one simple DTO for all operations is sufficient and also much easier to maintain for simple projects.
Suggestion, consider implementing an option in ABP Suite to use one simple DTO for all AGUD/ CRUD operations instead of separate ones.
BTW, the link in this sticky isn't working
https://support.abp.io/QA/Questions/954/We-are-listening-to-you
3 Answer(s)
-
1
Hi @improwise,
Thanks for the suggestion.
We are putting extra effort to make the generated code follow our best practices document. That is why we are separating the dto's.
I'll create an internall issue for your request, and the team will consider this option. But i don't think it will be done in near future.
-
0
OK, thanks.
One reason why this might be a good thing is if you want to use some other component library like DevExpress, Telerik etc. but still use ABP Suite to generate some boilerplate for it. Those components usually have just one DTO for all CRUD operations which might not be best practice but then again, the real world rarely is :)
Of course, this is still doable but it would require changing more of the generated code which would not be necessary if there was an option to use a simpler DTO structure.
I would guess that many customers of the Commercial version would build enterprise applications, for which you would normally have higher requirements regarding "data components" than typica free component libraries like Blazorize can offer.
-
0
One alternative way could perhaps be to add AutoMapper mappings so that you could convert between the generated DTOs if that is what you need, not sure how much extra work this would be though.
