You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Initial refactor and migration script to change Times objects in the database to only encompass a single session of a course. second_room (currently unused due to a bug) is removed, first_room is renamed to location, and a new session field is added to disambiguate the F and S sessions of a year-long course. A fall-winter Meeting will now have two Times objects linked to it, one for each session.
This moves the database in line with the direct timetable API response, which splits the fall and winter timeslots of a year-long course into different objects, and is a precursor to fixing the bug where year-long (Fall-Winter Y session) courses don't appear in the database.
...
Screenshots of your changes (if applicable)
Type of Change
(Write an X or a brief description next to the type or types that best describe your changes.)
Type
Applies?
🚨 Breaking change (fix or feature that would cause existing functionality to change)
X
✨ New feature (non-breaking change that adds functionality)
🐛 Bug fix (non-breaking change that fixes an issue)
🎨 User interface change (change to user interface; provide screenshots)
♻️ Refactoring (internal change to codebase, without changing functionality)
🚦 Test update (change that only adds or modifies tests)
📦 Dependency update (change that updates a dependency)
🔧 Internal (change that only affects developers or continuous integration)
Checklist
(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the [ ] into a [x] in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)
Before opening your pull request:
I have performed a self-review of my changes.
Check that all changed files included in this pull request are intentional changes.
Check that all changes are relevant to the purpose of this pull request, as described above.
I have added tests for my changes, if applicable.
This is required for all bug fixes and new features.
I have updated the project documentation, if applicable.
This is required for new features.
If this is my first contribution, I have added myself to the list of contributors.
I have updated the project Changelog (this is required for all changes).
After opening your pull request:
I have verified that the CircleCI checks have passed.
I'm unsure what the scope of this PR should be, and what I should add into a separate PR.
So far I've added the migration script and changed Times itself, and resolved any immediate errors in Tables.hs (i.e. Times to Time and Time' conversions) by temporarily slotting in null data. But there are other places in the code that expect Times to behave a certain way which I need to rewire (e.g. tests still pass, but the location doesn't show up at the moment). Time and Time' will also need to be changed to match, and in turn, everything that relies on them. What extent should I bring this PR to, and what should be separate?
The reason will be displayed to describe this comment to others. Learn more.
Hi @Purplegaze, you're definitely in the right direction here. For this task it'll be divided into multiple steps, so I've created a new branch on origin called y-course-refactor. As a first step, please re-make this PR, but using the target branch of Courseography:y-course-refactor instead of Courseography:master. You will continue to make other PRs onto that branch until we're done, at which point we'll make one file PR to merge y-course-refactor into master.
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
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.
Proposed Changes
Initial refactor and migration script to change Times objects in the database to only encompass a single session of a course.
second_room(currently unused due to a bug) is removed,first_roomis renamed tolocation, and a newsessionfield is added to disambiguate the F and S sessions of a year-long course. A fall-winter Meeting will now have two Times objects linked to it, one for each session.This moves the database in line with the direct timetable API response, which splits the fall and winter timeslots of a year-long course into different objects, and is a precursor to fixing the bug where year-long (Fall-Winter Y session) courses don't appear in the database.
...
Screenshots of your changes (if applicable)
Type of Change
(Write an
Xor a brief description next to the type or types that best describe your changes.)Checklist
(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the
[ ]into a[x]in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)Before opening your pull request:
After opening your pull request:
Questions and Comments
(See separate comment)