Implementing the view for showing the mentors in a program
Hi guys ,
I’ve been assigned to implement the following task.
In the ScholarX platform, Once the program reached the lifecycle state of MENTEE_APPLICATION_PERIOD and in the MENTEE_VERIFICATION_PERIOD a mentee can apply for mentors. So my task is to list down all the mentors that available in that particular program.
When I starting to code I noticed that the directory structure needs to be changes for MentorApplication and EditMentorApplication. Currently, it’s under Home -> components and it should be Home -> scenes. @jaye
Corrected structure :
I also have some things to be clarified:
Do I have to create the dynamic button for the program card. Ex: for this scenario the button should be Request for a mentor .
Is creating dummy buttons for request and cancel enough for this task?
What about this for the URL /program/:programId/mentee/mentor-request
Thanks @anjisvj for the detailed update! @EngTeam take this as an example.
Let’s do it in another task, after implementing all possible functionalities.
Yes. It’s okay for the initial PR. Then you can implement the apply/edit mentee application functionality. (You can use the same thread. Add the details of the application process in the requirement and make the title generic. Ex. Implementing the mentee application functionality in scholarx)
I think program/{:programId} would be ideal.
list all applied mentors of the logged-in user (in the mentee application period)
Hi guys ,
I’ve been assigned to implement the following task.
In the ScholarX platform, Once the program reached the lifecycle state of MENTEE_APPLY_PERIOD a mentee can apply for mentors. So my task is to create the form that a mentee get to fill in order to apply for a mentor.
As we discussed the mentor request modal needs to be changed. Currently, I don’t have permission to edit the wireframe. As soon as I got the permission I will update it.
When It comes to editing the doc URL, I need to GET the mentee so I had to change the the route from program/:programId to program/programId/mentee/menteeId. Let me know your thoughts. @jaye
My point is not between using a model and and a new page.
The mentee id is unique for each application. And I don’t think the API should expect the mentee id to send the application details. It should expect the mentor ID because we can extract the mentee id by using the userId (already in the session) and the mentorID.