Added manual grading to the frontend. There is a bug where the api doesn't create the releasedAt date when updating a submission score entity so I hardcoded a date.
Proposed changes
Added a button that makes textfields appear for manual grading of submissions.
Resolves #74
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)
Further comments
Right now,there is a bug when updating a submission score which requires a releasedBy field to be passed through the frontend instead of being created by the backend. This field is hardcoded on the frontend and needs to be removed in the future.
Added manual grading to the frontend. There is a bug where the api doesn't create the releasedAt date when updating a submission score entity so I hardcoded a date.
Proposed changes
Added a button that makes textfields appear for manual grading of submissions.
Resolves #74
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
Right now,there is a bug when updating a submission score which requires a releasedBy field to be passed through the frontend instead of being created by the backend. This field is hardcoded on the frontend and needs to be removed in the future.