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

Add "sections" aggregate endpoint to course endpoint #227

Open
jpahm opened this issue Oct 23, 2024 · 3 comments · May be fixed by #234
Open

Add "sections" aggregate endpoint to course endpoint #227

jpahm opened this issue Oct 23, 2024 · 3 comments · May be fixed by #234
Assignees
Labels
L2 A task suitable for someone who is comfortable implementing features.

Comments

@jpahm
Copy link
Contributor

jpahm commented Oct 23, 2024

Currently, it can be inconvenient and overcomplicated for our end users to perform some common aggregate operations such as getting all of a course's sections.

As such, we should add the following endpoints which immediately aggregate and return matching courses' sections:

  • Query based: GET /course/sections (allows for querying like the base course endpoint)
  • ID specific: GET /course/{courseId}/sections (gets sections only for a specific course)
@jpahm jpahm added the L2 A task suitable for someone who is comfortable implementing features. label Oct 23, 2024
@mikehquan19
Copy link
Contributor

Can I be assigned this ? This is fun.

@jpahm
Copy link
Contributor Author

jpahm commented Oct 31, 2024

Can I be assigned this ? This is fun.

I'm glad it's fun, the work on these issues is very helpful!

You are good to work on it :)

@mikehquan19
Copy link
Contributor

I completed this task and committed it in the same pull request as task #230.
Thank you.

@jpahm jpahm linked a pull request Nov 4, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
L2 A task suitable for someone who is comfortable implementing features.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants