Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Submission problem score #2

Merged
merged 51 commits into from
Feb 21, 2023
Merged

Submission problem score #2

merged 51 commits into from
Feb 21, 2023

Conversation

alans-42
Copy link
Owner

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 x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • 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.

  • 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


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...

jmabramo and others added 30 commits October 5, 2022 17:06
Added Submission Problem Score Model
Submission Problem Score rename release to releasedAt
added SubmissionProblemScore router
Thanks

Co-authored-by: Jesse Hartloff <[email protected]>
jessehartloff and others added 20 commits October 19, 2022 17:51
- Changed release to releasedAt
- Tests are successful
…core

Submission problem score - Serializer
submission problem score allow null
-Add path for updating a record
-Removed path to get all records
-Added path to get all records for a specific submission
Copy link
Owner Author

@alans-42 alans-42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good

@alans-42 alans-42 closed this Feb 21, 2023
@alans-42 alans-42 reopened this Feb 21, 2023
@alans-42 alans-42 merged commit b6ec8a4 into master Feb 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants