New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0209 update settings to complete rollover #1586
Conversation
9ea6b94
to
72adf30
Compare
Need to lock down none moveable settings
Retained hardcore value for recruitment cycle year
This is so it relies on settings current recruitment cycle year (rollovered) insteads.
This is to constrained recruitment year to the rollovered cycle
The tests needs to be within the current recruitment year (rollovered).
This is so that the tests operate beyond the realm or current recruitment cycle.
72adf30
to
49f570d
Compare
# Note: the concept of recruitment cycle here is ethereal. | ||
# it is tied to a recruitment cycle that is associated to | ||
# Settings.allocation_cycle_year | ||
allocation_recruitment_cycle |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the settings we call this allocation cycle
. That makes more sense than allocation recruitment cycle
, in my mind at least, should we use that or is the longer version correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving as we're short on time.
Context
Rollover
Changes proposed in this pull request
Rollovered
Guidance to review
Best to view by commits
Config change cause some broken tests due to hardcoring.
As well as the ethereal nature of recruitment cycle vs allocation year over allocation
Checklist