consume and show section specific titles#245
Open
JustinH11235 wants to merge 3 commits intogt-scheduler:mainfrom
Open
consume and show section specific titles#245JustinH11235 wants to merge 3 commits intogt-scheduler:mainfrom
JustinH11235 wants to merge 3 commits intogt-scheduler:mainfrom
Conversation
This was referenced Oct 26, 2025
1 task
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.
Summary
No ticket related.
I noticed for CS 8803 the section title shown was not the sections actual title, it was whatever the first section for CS 8803's title was, which happened to be Computer Law or something.

This is because the code only tracks a single title for the course itself, not specific sections. This PR adds that data to the crawler's section type.
Note: I had to add the extra field at the end of the tuple type for compatibility with GT scheduler's frontend parsing because tuples are parsed by their order, not the names of their field. This means you should be able to roll the backend PR first gt-scheduler/crawler-v2#18, then roll this PR to change the frontend. As a side-note, I think this is the disadvantage of using tuples, if these were records, it would likely be easier to upgrade the types.
This is what the final product looks like after both backend and frontend roll:

Potential Future Work:
course.titleto use the first section's title, so that you can later removecourse.titlein the backend afterward.Checklist
yarn lint and format
How to Test
Look at an example like CS 8803.