Revise API Request/Response Objects #223
Labels
enhancement
Improvements to existing features with relevant impact
nice to have
Low priority issues that improve quality of life
For EF29 or the future, it may be nice to revise the HTTP API to use DTOs instead of the real database records.
Currently, we have some controllers which are using the raw records like DealersController:
And some who don't like FursuitController:
Working with the raw DB records can cause some problems like ID collisions and exposing sensitive or unneeded information.
I suggest could we implement a uniform DTO system for each request/response/database record.
This also relates to #131
The text was updated successfully, but these errors were encountered: