Update submission column parsing#67
Merged
Merged
Conversation
This was referenced May 23, 2026
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
1 participant
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.
Summary
Updates submission parsing logic to fix courses using
FirstandLastname instead of a singleFull NamecolumnDetails
Previously we assume the submission column is 3 or 4 if the course has sections. This hardcoded value also breaks if the name column is split into First & Last (2 columns) instead of Full (1 column) name (meaning the submission column would be 4 or 5).
This switches the parsing to iterate from the end which should be stable (submission column should always be 3rd from the end before
EditandRemovecolumns). This also avoids the dependency on the English word.Checks
Team to Review
Mention the name of the team to review the PR
Reference to the issue
Resolves #66
Supercedes #48