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
Shows details (aka whatever the course record looks like)
Has a link to update the course if the user can update the course (just an update button somewhere on the page)
Shows the assignments for a course
Assignment name, due date,
Allow reorder of assignments by "default" (active, then by due date), due date, active, name
Some sort of filter for assignments by, default to all category, name, due date, active
Show way to access grade book page & roster page (maybe some navigation items at the top or bottom?) (These also should only appear on the page for users who actually have access to them)
The text was updated successfully, but these errors were encountered:
Quick question regarding the API calls needed for this issue:
For the api/assignments GET request I'm assuming I'd be using to retrieve the assignments for the course, it appears that using the current functionality that call would return all assignments in the database. Is this something that I should be accounting for in my implementation (getting the assignments, and then filtering by courseId), or will getting assignments by courseId be a later feature and I'd be ok building the page with the general GET request for now.
Getting a list of all the assignments and getting assignments for a user, the response shape will be the same. So just use the existing endpoint to get a list of assignments.
We will likely have to update that endpoint at some point to only give back your assignments. Either way nothing should really change in the client
Feature request
/courses/:coursId
The text was updated successfully, but these errors were encountered: