codeyourfuture / class-planner Goto Github PK

Hello. Myself and another TA tried cancelling our attendance to a class but it didn't work. The input form for the email popped up but then submitting it didn't do anything. This makes it difficult to know if someone has changed their mind. I'm on Linux Firefox. Thanks!

JFYI :
When user browse http://localhost:3000/coursecalendar/ and click on attend then click on browser back button and back to the course calendar page , multiple attend forms appear below of each ClassCard .

I dont know its bug or what but anyway I've reported as issue here.

https://github.com/AKaramifar/Class-Planner/blob/6982dbd3b305f1438de1f86a210c578b1d195063/backend/models/Booking.js#L4

There is an issue when a volunteer try to sign up with a valid uppercase email, I have got a message saying email is not valid

As an admin when I go to the upcoming class page (https://cyf-class-planner.herokuapp.com/upcomingclass/) , and when cancel button clicked then it only shows the loading .

it must check for http:// or https:// at the first of URL and accept it or the software must detected the lack of protocol (http , https) or add it automatically .

Error appear when run backend
Error: ENOENT: no such file or directory, stat '/Users/babak/Projects/CYF/Final Project/Class-Planner/frontend/build/index.html'

Server.js line 22 , wrong path

this setting should be for Heroku , but is it possible solve it in dev ?

if netlify.toml is work, is it necessary we keep this line ( server.js Line 22) ?

so please try to give a message to the admin when he/she try to edit a course with classes, to say this course can not be updated as it does have classes and thanks

Update a class at the http://localhost:5000/api/v1/classes does't work with PUT method. (backend)

Problem

Our current setup of this application includes hardcoded authentication on our front-end and no authentication on our back-end endpoints. This leaves our data open to public visibility, which contains personal information (Names and Email addresses).

In order to fix this, we should implement some level of security on API backend and an improved method of authentication on the front-end to ensure that the password for administration cannot be retrieved from the front-end, and that our api endpoints can't be hit without authentication.

Solution

The easiest implementation of a solution with the current setup of our APIs would be to introduce a JWT Token requirement for the backend authentication.

1. Admin logs into the frontend
2. If successful login, a JWT token is generated (expires in 15mins? TBC.)
3. JWT token is passed as a parameter within requests (/:token/cities), to make minimals changes to the API.
4. If JWT is invalid (or has expired), the request is blocked as forbidden, else the data is passed back to the client

Duplication happen for newcouse when double click on add new course button.