Fix remarks for annotations on autograder output#1579
Merged
Conversation
victorhuangwq
approved these changes
Aug 23, 2022
| <h2 style="margin-top: 1em">Remarks</h2> | ||
|
|
||
| <ul> | ||
| <!-- TODO: Make order of annotations consistent with order of file list --> |
Contributor
There was a problem hiding this comment.
Ah so this is a TODO for the future?
Member
Author
There was a problem hiding this comment.
Yup, it is a TODO to track the second "bug" reported by the 122 team (The order of annotations in the student feedback when they click on the score is not the same as the order when you look at the file page)
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
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.
Description
When
annotation.position = -1, setfilenametoAutograder Outputinstead.Motivation and Context
A bug noted by the 122 team is that annotations on the autograder output (when
annotation.position = -1) appear to reference the last file in the file tree instead.Looking at
viewFeedback.html.erb, the current logic for choosingfilenameis@files && annotation.position ? Archive.get_nth_filename(@files, annotation.position) : @submission.filename.When we have a single file submission,
@filesisniland sofilenameis@submission.filename(i.e. the last file).Similarly, with an archive submission,
filenameisArchive.get_nth_filename(@files, annotation.position), which evaluates to@files[annotation.position][:pathname]whereannotation.position = -1. In particular, we are accessing index-1, i.e. the last file.This PR remedies the logic by explicitly handling the
annotation.position = -1case.How Has This Been Tested?
Styleproblem.Before changes

After changes

Types of changes
Checklist:
overcommit --install && overcommit --signto use pre-commit hook for linting