When making a batch request (/:campus/classes), the quarter and year parameters are passed in the URL (as query parameters) rather than in the class object of the resources. This means that when requesting for multiple classes in different quarters or different years, a separate request is required. It'd make more sense if all of these could be grouped into one batch request.
Ideally, the batch endpoint could take resources like these:
Retaining the same possible combinations: CRN, dept, or dept + course.
I also threw campus in there for the same reason; the endpoint would therefore be /classes.
It'd be more efficient (one batch request for any data in the entire database) and would probably allow for more use-cases.
When making a batch request (
/:campus/classes), thequarterandyearparameters are passed in the URL (as query parameters) rather than in the class object of theresources. This means that when requesting for multiple classes in different quarters or different years, a separate request is required. It'd make more sense if all of these could be grouped into one batch request.Ideally, the batch endpoint could take resources like these:
{ campus: string, CRN: number, year: number, quarter: 'summer' | 'fall' | 'winter' | 'spring' }Retaining the same possible combinations:
CRN,dept, ordept+course.I also threw
campusin there for the same reason; the endpoint would therefore be/classes.It'd be more efficient (one batch request for any data in the entire database) and would probably allow for more use-cases.