You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, it can be inconvenient and overcomplicated for our end users to perform some common aggregate operations such as getting a section's course or the professors which teach the section.
As such, we should add the following endpoints which immediately aggregate and return matching sections' courses or professors:
Courses:
Query based: GET /section/course (allows for querying like the base section endpoint)
ID specific: GET /section/{sectionId}/course (gets course only for a specific section)
Professors:
Query based: GET /section/professors (allows for querying like the base section endpoint)
ID specific: GET /section/{sectionId}/professors (gets professors only for a specific section)
The text was updated successfully, but these errors were encountered:
jpahm
added
the
L2
A task suitable for someone who is comfortable implementing features.
label
Oct 23, 2024
Currently, it can be inconvenient and overcomplicated for our end users to perform some common aggregate operations such as getting a section's course or the professors which teach the section.
As such, we should add the following endpoints which immediately aggregate and return matching sections' courses or professors:
Courses:
GET /section/course
(allows for querying like the base section endpoint)GET /section/{sectionId}/course
(gets course only for a specific section)Professors:
GET /section/professors
(allows for querying like the base section endpoint)GET /section/{sectionId}/professors
(gets professors only for a specific section)The text was updated successfully, but these errors were encountered: