Updated the assignment detail page. Changed the styling and updated the api calls to match the newest versions. However, the requests seem to give back a 404 error so there may be some error in the backend?... or maybe I missed something.
Proposed changes
Updated the Assignment Detail Page to be better styled than it currently was. It was very ugly looking so it was not hard :( .
Resolves #104
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)
Updated the assignment detail page. Changed the styling and updated the api calls to match the newest versions. However, the requests seem to give back a 404 error so there may be some error in the backend?... or maybe I missed something.
Proposed changes
Updated the Assignment Detail Page to be better styled than it currently was. It was very ugly looking so it was not hard :( .
Resolves #104
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.