Skip to content
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

Create Class Videos CRUD Routes #30

Open
h0ethan04 opened this issue Dec 4, 2024 · 0 comments · May be fixed by #39
Open

Create Class Videos CRUD Routes #30

h0ethan04 opened this issue Dec 4, 2024 · 0 comments · May be fixed by #39
Assignees
Labels

Comments

@h0ethan04
Copy link
Collaborator

h0ethan04 commented Dec 4, 2024

Description

  • Your task is to create backend routes for some of the tables. These routes will be used as a way to retrieve and put information into the corresponding tables.

Instructions

  • Add the backend .env file in /server (can be found here)
  • Place routes inside a file named class_videos.js located in /server/routes/
    • make sure each set of routes per table, are in their corresponding files
      • i.e. Class routes should be in a class.js file and class_enrollments routes should be in a class_enrollments.js
      • feel free to check out the Sample CRUD Routes that were already provided
  • Create CRUD routes based on the Project Architecture Document
  • When completed make sure to test with Postman and the neondb database (you will need the backend .env file if you don’t have it already)
  • Now add your new classVideosRouter in server/src/app.ts similarly to how it's currently adding usersRouter

Notes

  • See Project Architecture document for routes

Acceptance Criteria

  • All routes work as expected and return the values indicated by the Output column
  • Include pictures of your POSTMAN testing
  • When creating your pull request follow the steps in the Pull Request Tips

Resources

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants