-
Notifications
You must be signed in to change notification settings - Fork 1
Application priority bug #1694
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
Application priority bug #1694
Conversation
…ty is reorganized
nemisis84
left a comment
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.
Haven't taken a deep look into this., but leaving a comment anyway The algorithm itself is probably fine and it seems to work in the browser.
The test should be covering and documenting the edge cases. However, I think all tests should have a docstring describing the test case.
nemisis84
left a comment
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.
Only approving because I have to. But nice that you added docstrings
💡 replaced this:#1594
There was a bug which made applicant priority of positions incorrect. This is because when priority is manipulated the total count of applications was including withdrawn applications.
This was the case both when a new application was created, but also when applications where withdrawn.
There also is a bug where the priority is set incorrectly in the scenario when the applicant applies for a position which they previously had withdrawn the application from (could also be described as "re-activating" the application). The application gets the priority it had when it was withdrawn, which seems like unwanted behavior. I think the behavior should be that the "re-activated" application should get the lowest priority, like when the applicant applies for a position for the first time.