# Developing ScholarX backend **URL:** \ **Category:** ScholarX\ **Created:** [August 18, 2020, 8:00am UTC](https://sef.discourse.group/t/developing-scholarx-backend/169 "2020-08-18T08:00:06Z")\ **Posts on this page:** 8\ **Page:** 2
**Author:** ![piumal1999](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/piumal1999/32/274_2.png) [@piumal1999](https://sef.discourse.group/u/piumal1999)\ **Post date:** [October 17, 2020, 10:20am UTC](https://sef.discourse.group/t/developing-scholarx-backend/169/21 "2020-10-17T10:20:40Z")
> [@YohanAvishke](#): > > We can simplify the resource paths: > `curl --location --request PUT 'mentees/{menteeId}/status?programId='` @anjisvj could you please update the documentation with this ---
**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:** [October 17, 2020, 4:19pm UTC](https://sef.discourse.group/t/developing-scholarx-backend/169/22 "2020-10-17T16:19:45Z")
> @piumal1999 could you please review and merge this ASAP ---
**Author:** ![piumal1999](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/piumal1999/32/274_2.png) [@piumal1999](https://sef.discourse.group/u/piumal1999)\ **Post date:** [October 17, 2020, 4:37pm UTC](https://sef.discourse.group/t/developing-scholarx-backend/169/23 "2020-10-17T16:37:33Z")
Is ‘update state of a program’ a non-reversible action? @YohanAvishke ---
**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:** [October 17, 2020, 5:45pm UTC](https://sef.discourse.group/t/developing-scholarx-backend/169/24 "2020-10-17T17:45:36Z")
Yes for the current stage. But in case a requirement arises it’s flexible to change ---
**Author:** ![piumal1999](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/piumal1999/32/274_2.png) [@piumal1999](https://sef.discourse.group/u/piumal1999)\ **Post date:** [October 18, 2020, 5:11pm UTC](https://sef.discourse.group/t/developing-scholarx-backend/169/25 "2020-10-18T17:11:19Z")
The directory structure of test controllers are not similar to the directory structure of controllers. It is possible to use the same test controller file for two separate controllers. But i think it’s better if we can keep the same directory structure in test controllers and controllers to make it less complex. So i created an issue for that: > Previous structure: ├── controller │ ├── MenteeControllerTest.java │ ├── MentorControllerTest.java │ └── ProgramControllerTest.java └── service New structure that i suggest: ├── controller │ ├── admin │ │ ├── MenteeControllerTest.java │ │ ├── MentorControllerTest.java │ │ └── ProgramControllerTest.java │ └── ProgramControllerTest.java └── service Sent a PR for that. Please review and merge > ---
**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:** [October 19, 2020, 2:45am UTC](https://sef.discourse.group/t/developing-scholarx-backend/169/26 "2020-10-19T02:45:58Z")
Awsome job @piumal1999 😍 ---
**Author:** ![piumal1999](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/piumal1999/32/274_2.png) [@piumal1999](https://sef.discourse.group/u/piumal1999)\ **Post date:** [October 22, 2020, 5:48pm UTC](https://sef.discourse.group/t/developing-scholarx-backend/169/27 "2020-10-22T17:48:38Z")
With the previous discussions, we have found some minor bugs and issues in the scholarX backend that needed to fixed. The requirements are mentioned below. - Add a JSON response payload to DELETE endpoints - Add a column for mentor application - Rename questionnaire to the prerequisite - Change the program state MENTEE\_APPLY to MENTEE\_APPLICATION I created issues for these in the github repository. I’m working on these issues and I’ll use this thread for the updates and discussion Related links: > [@SchoalrX platform v1: Progress evaluation](https://sef.discourse.group/t/schoalrx-platform-v1-progress-evaluation/192/2): > > Mid week update on 2020-10-21T03:00:00Z (UTC) Attendees@Gravewalker, @YohanAvishke, @jaye, @piumal1999, @anjisvj, @Gimhan_minion ScholarX Backend Yohan completed the edit Program API Edit program Fix the changing state Piumal sent a PR for the directory structure of the backend Created issues for the bugs Yohan is working on the API documentation Few more endpoints need to be added [https://docs.google.com/document/d/1pUfcvqtR9I9YqPe79jGm8j8MCWp3Yvr2RwTaOHRSKD8/edit#](https://docs.google.com/document/d/1pUfcvqtR9I9YqPe79jGm8j8MCWp3Yvr2RwTaOHRSKD8/edit#) Next Steps … > [@Building a mock API server for the ScholarX API](https://sef.discourse.group/t/building-a-mock-api-server-for-the-scholarx-api/186): > > Hello there, Since the API gateway task takes a few more days to get delivered and we are running out of time for the initial phase, building a mock server is essential to continue the frontend development. The requirement is to build a mock API server that is smart enough to simulate the real API. I thought of initializing this task, I’ll update my work with this thread. ---
**Author:** ![piumal1999](https://yyz2.discourse-cdn.com/free1/user_avatar/sef.discourse.group/piumal1999/32/274_2.png) [@piumal1999](https://sef.discourse.group/u/piumal1999)\ **Post date:** [October 22, 2020, 6:48pm UTC](https://sef.discourse.group/t/developing-scholarx-backend/169/28 "2020-10-22T18:48:36Z")
Fixed the issue with this pull request: > Please review and merge [Previous page](https://sef.discourse.group/t/developing-scholarx-backend/169.md?page=1)