Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply
[ ] Bugfix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. This is simply a reminder of what we are going to look for before merging your code.
[X] My changeset covers only what is described above (no extraneous changes)
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged downstream
Further comments
I'm not entirely sure if I implemented the filter described in the issue correctly (I made it a "group by" dropdown, with the elements being the category described).
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
This page shows the general info of the course, alongside some buttons which direct to specific actions a user can take (view the roster/gradebook if a user-course object exists for the user, and edit course if the user is an instructor). The page also shows all of the assignments associated with the course.
zaida04
commented
1 year ago 
Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce? Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. This is simply a reminder of what we are going to look for before merging your code.Further comments
I'm not entirely sure if I implemented the filter described in the issue correctly (I made it a "group by" dropdown, with the elements being the category described).
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
This page shows the general info of the course, alongside some buttons which direct to specific actions a user can take (view the roster/gradebook if a user-course object exists for the user, and edit course if the user is an instructor). The page also shows all of the assignments associated with the course.
beetosu included the following code: https://github.com/UBAutograding/devU-client/pull/41/commits