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, the only way to get information from this page is by invoking getCourseSections, which is an expensive call as it needs to make several round-trips to create the response. For advanced users, they can reduce the RTT by making one less call (Class Schedule Listing page) if that page is saved (and therefore the CRNs) since this page does not change very frequently.
The text was updated successfully, but these errors were encountered:
is this still relevant / what do you mean by this? caching the sections page in the npm package? Our current implementation (as of the latest API refactoring) gets the Class Schedule Listing page, parses it, and returns it.
Currently, the only way to get information from this page is by invoking
getCourseSections
, which is an expensive call as it needs to make several round-trips to create the response. For advanced users, they can reduce the RTT by making one less call (Class Schedule Listing page) if that page is saved (and therefore the CRNs) since this page does not change very frequently.The text was updated successfully, but these errors were encountered: