-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Endpoints for handling contests created by the admin #9
Comments
Please describe the issue in detail, and add relevant wireframes in the description itself. |
Change the description of the issue, and list out all the api endpoints you are planning to create, what the DB schema will look like. |
Backend for saving and providing the details of new and past contests by the admin. DB schema will contain all fields for every specific page along with respective unique id i.e. every contest will also have user id,a unique contest id,the basic info of that contest will be having already mentioned unique ids of user and contest and will also have a basicinfo id and so for the others |
Please edit the description and add the above content there only. |
Backend for saving and providing the details of new and past contests by the admin.
GET,POST,PUT,DELETE routes will be used in all specific pages
/mycontest->for all the contests created by the admin
/mycontest/new->to create a new contest
/mycontest/{contestid}->to render the specific contest
/mycontest/{contestid}/basicinfo->for the basic info of that contest
/mycontest/{contestid}/adminrights->for the admin rights of that contest
/mycontest/{contestid}/questions->for all the questions of that contest
/mycontest/{contestid}/questions/{questionid}->for a particular question of that contest
DB schema will contain all fields for every specific page along with respective unique id i.e. every contest will also have user id,a unique contest id,the basic info of that contest will be having already mentioned unique ids of user and contest and will also have a basic info id and so for the others
Rest issues will be updated further.
The text was updated successfully, but these errors were encountered: