单独的 DTO 用于发布和放置请求 & 嵌套 json 作为发布 model

Question

I have two questions about RESTful api.

1. Can we have separate DTO for GET, POST and PUT request? Is it good practice
or can I make one abstract class with common properties and then inherit from it?

2. Is sending nested json in POST request a good practice?

As did in following article:
https://code-maze.com/net-core-web-development-part6/

Answer 1

1. Yes, and more to the point, you should . A DTO is a representation of a particular group of data in a particular scenario. That data can and will be different between different request types. Any time there's different data being transferred, there should be a different DTO to represent it.

   You can utilize inheritance if you like and it makes sense. However, be aware that due to the way modelbinding works, you will still need to use your concrete, derived classes as params, not some base class. The modelbinder will instantiate the class specified by the param (so it can't be abstract), bind any request values represented on that class, and discard the rest. So if you bind to BaseClass , all you will have is BaseClass , not DerivedClass , even if the request body was a representation of DerivedClass . If you then attempted to downcast to DerivedClass , all the properties specific to DerivedClass would be null/default.

2. It is neither good nor bad practice. JSON is an object representation format. If your object has nested objects, then your JSON would have nested JSON.

Answer 2

1. Can we have separate DTO for GET, POST and PUT request?

DTOs are not created based on the request type, instead DTOs are created for entities. For example you have a Customer entity, for the Customer entity you will create a Customer DTO and the same Customer DTO can be used for GET, POST and PUT requests of Customer entity.

Can I make one abstract class with common properties and then inherit from it?

Yes you can use inheritance while creating your DTOs but I would say thats over complication for no added value and keep in mind that inheritance, if not used properly can increase coupling in system.

2. Is sending nested json in POST request a good practice?

As Chris mentioned in his answer, if your object has a nested object then your JSON will have nested JSON.