[Feature:API] Get list of student's gradeables#11532
Merged
Merged
Conversation
automateprojectmangement
Bot
moved this from Seeking Reviewer
to Work in Progress
in Submitty Development
IDzyre
changed the title
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #11532 +/- ##
============================================
- Coverage 21.67% 21.64% -0.04%
- Complexity 9802 9818 +16
============================================
Files 268 268
Lines 36724 36777 +53
Branches 490 490
============================================
Hits 7960 7960
- Misses 28278 28331 +53
Partials 486 486
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
github-actions
Bot
added
the
Abandoned PR - Needs New Owner
IDzyre
removed
the
Abandoned PR - Needs New Owner
github-actions
Bot
added
the
Abandoned PR - Needs New Owner
Member
Author
|
Closing this as it will not be updated for a few months, and to not clog the existing list of PRs. Will re-open when ready to continue. |
Member
Author
|
Re-opening this because I am picking it back up. |
IDzyre
commented
Mar 2, 2026
| */ | ||
| #[Route('/api/{_semester}/{_course}/gradeable/{gradeable_id}/values', methods: ['GET'])] | ||
| public function ajaxGetGradeableValues(string $gradeable_id): JsonResponse { | ||
| $user_id = $_GET['user_id'] ?? ''; |
Member
Author
There was a problem hiding this comment.
Removing this, as other endpoints do not require a user_id to be passed. Still allowing it as an optional parameter for an instructor, but students do not need to send it, since we can access it from core->getUser()->getId()
github-actions
Bot
added
the
Abandoned PR - Needs New Owner
IDzyre
removed
the
Abandoned PR - Needs New Owner
williamjallen
requested changes
May 16, 2026
This can be added back later if requested, but to get this merged it is being removed.
github-project-automation
Bot
moved this from Seeking Reviewer
to Work in Progress
in Submitty Development
IDzyre
moved this from Work in Progress
to Awaiting Maintainer Review
in Submitty Development
williamjallen
approved these changes
May 19, 2026
williamjallen
left a comment
williamjallen
left a comment
Member
There was a problem hiding this comment.
Looks good to me. Let's wait to merge this until the CI is back to passing unless it's really blocking something else you're working on.
Member
Author
|
It is what the VS Code plugin repo is based on, so the sooner the better. I will see if I can fix (at least a bulk) of CI tonight, unless someone else fixes it first. |
github-project-automation
Bot
moved this from Awaiting Maintainer Review
to Done
in Submitty Development
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why is this Change Important & Necessary?
The Submitty API is lacking in features that would allow for creating a VS code extension. Specifically, getting a list of gradeables that a user has access to for a given course, and a route to verify the user logged in.
Also, the current "get gradeable values" route has the full grade passed, but not the reason for each testcase passing/failing.
What is the New Behavior?
A route has been added
base_url/api/<term>/<course>/gradeablesthat returns a GradeableList converted to Json of the currently available gradeables to the given user.An instructor can also use this, and specify a given user ID if they would like to get gradeables for a student.
A lot more information has been added to the
.../valuesendpoint to give the extension more to work with.What steps should a reviewer take to reproduce or test the bug or new feature?
Review the code, or use an API testing tool (such as Postman) to test the API route successfully returns values for a given user.
Other information
This won't impact current installations or require any sysadmin actions.