hackru / mentorq-backend Goto Github PK

Since we want to integrate LCS slack-dm-link endpoint with mentorq, we could potentially do this from the backend. This may also be a frontend issue.

When the repo is freshly cloned, there is an exception due to the migrations not being run properly. Needs to be investigated to find and fix the issue

LCS has changed how authentication works and we need to make the necessary changes to be compliant with it. It is highly likely that parts of backend might not work entirely after that has been pushed

Since the frontend is thinking of developing a feature for feedback, we should develop an endpoint to store information regarding it.

As of right now, the feedback endpoint should be able to handle information regarding:

• The name of the mentor who helped the mentee (we could potentially store other information, we just need to retrieve this)
• The name of the mentee who was helped (same goes for this as well)
• Star rating given to the mentor
• Feedback in the form of text

This will likely affect tables names in our sqllite database but having folder names that make more sense could help newer developers that join mentorq and want to develop on the backend.

We likely want to restrict access to the backend dev site as the debug logs can have important information in them and be a security issue. We could restrict based on IP through django if necessary (https://django-iprestrict.readthedocs.io/en/latest/).

We should make the API documentation look a bit cleaner and potentially move it to github wikis to not take up much space in the readme while at the same time being consistent with our LCS repo.

Similar to #14 but since it is for the actual hackathon we may need to consider some other tools or scrap continuous integration for it altogether.

This will allow us to provide a consistent dev environment since there have been issues setting up Django in the past. This will also allow front-end to seamlessly run the back-end without having to deal with unexpected Django errors

Potentially connect our tests with Travis so we can always have tests checked when we push to branches.

Setup a basic script to run all of the migrations necessary for our mentorq backend

It is unrealistic for mentee's to create unlimited number of tickets so.. need to add a hard limit to the number of tickets that can be opened at a time by a given mentee

In order to support feedback editing and checking if it exists without making extra requests, it needs to be added to the ticket

We can have constantly deployment for a dev endpoint for us to test via heroku on a development branch. We have a limited amount of space but seeing the size of the database currently it shouldn't be an issue.

Update the mentorq start script to take in a path as an option to run both the backend in the frontend. If no path is provided only run the backend.

Since role gets sent along with access and refresh token, changes in permissions won't be reflected if the front-end stores it early on when receiving the tokens for the first time. Instead we can maybe send it by embedding into the payload of the access token itself so that role updates are reflected accordingly.