# Developing AcadeMix Backend

**URL:** <https://sef.discourse.group/t/developing-academix-backend/94>\
**Category:** Development\
**Created:** [May 23, 2020, 2:47pm UTC](https://sef.discourse.group/t/developing-academix-backend/94 "2020-05-23T14:47:45Z")\
**Posts on this page:** 1\
**Showing post:** 33

<div class="post-metadata">

**Author:** ![YohanAvishke](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/yohanavishke/32/106_2.png) [@YohanAvishke](https://sef.discourse.group/u/YohanAvishke)\
**Post date:** [June 16, 2020, 2:38am UTC](https://sef.discourse.group/t/developing-academix-backend/94/33 "2020-06-16T02:38:07Z")

</div>

Code review notes

**Description**

A code review was held to do a demonstration and to review the code of admin APIs developed for Academix.

* * *

**Attendees**

@jaye  
@Gravewalker  
@anjisvj  
@piumal1999

* * *

**Notes**

- Return the created object as the response in the create APIs
- Refactor all the admin APIs including data retrieval APIs to use the Entity classes itself instead of the DTOs and Projections.  
The possibility of this change has to be tested before implementation. Therefore this will be implemented in a separate PR.
  - This change will effectively remove all the DTOs and Projection classes.
  - This will remove lot of validation code from the service layer.
  - After this change, we can update an entity’s data and it’s translations using a single API.

* * *

**Next steps**

- Bring the PR to a mergeable state
- Start working on the second note I have mentioned above

---

_[View the full topic](https://sef.discourse.group/t/developing-academix-backend/94)._