-
Notifications
You must be signed in to change notification settings - Fork 23
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
Add rolling admission field to career opportunity #3300
Conversation
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.
Får vi ikke samme effekt av å si at frist + snarest = løpende?
Nå overkjører snarest alltid fristen, men det må den jo ikke.
snarest = not søknader_vurderes_bare_etter_fristen?
Evt. bytte navn på snarest til "rolling admission" eller noe annet som bedre reflekterer hva det innebærer
] | ||
|
||
operations = [ | ||
migrations.RemoveField( |
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.
Bruk en rename i stedet?
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.
Hvorfor er det bedre? Django autogenererte migrationen.
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.
Fordi hvis ikke sletter du eksisterende data?
Django "scaffolder" bare, du må selv si hvorvidt det du gjør er en rename eller et nytt separat felt—hvordan skal django kunne detektere forskjellen?
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.
Veldig godt poeng, hadde ikke tenkt på det. Fikser!
dotkom/onlineweb-frontend#745
Endret navn fra deadline_asap til rolling_admission.