Skip to content
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

finalize user admission priorities for backend #987

Merged
merged 14 commits into from
Jun 16, 2024
Merged

Conversation

magsyg
Copy link
Contributor

@magsyg magsyg commented Feb 13, 2024

closes #984

@magsyg magsyg changed the title finalize priorites for backend finalize user admission priorities for backend Feb 13, 2024
@magsyg magsyg self-assigned this Feb 13, 2024
backend/samfundet/views.py Outdated Show resolved Hide resolved

"""
admissions_for_user = RecruitmentAdmission.objects.filter(recruitment=self.recruitment, user=self.user)
# Use order for more simple an unified for direction
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Skjønner ikke

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hva er det du ikke skjønner?
Får tak i alle admissions for bruker og recruitment

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mistenker at man kan gjøre dette enklere, men det avhenger av noen ting sikkert.
Er det validering på at man ikke kan ha samme priority, er vi sikret mot feil tilstand?

Copy link
Member

@emilte emilte Jun 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Er høy eller lav prio best? Er det som rekkefølge slik at 1 er øverst?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lav, er mer rangering

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gjerne svar på alle spørsmålene. Skal komme opp med et forslag, tror jeg har en god ide.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Den er sikret mot at gjennom bruk av denne, så kan ikke flere ha samme rangering, siden den vill bytte opp plassering og sortere.
Den PR er lagd for å organisere og omgjøre prioriteringer.
Den kan settes manuelt til samme, men den beskyttelsen vil være i en annen PR.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Så det er en db constraint på vei inn?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Det er ikke en DB constraint nei, det kan settes manuellt, og da sier ingenting at det ikke er mulig.
En DB constraint i dette tilfellet kan foresake en form for deadlock, hvor når den bytter om så vil det være et tilfelle 2 har samme verdi, og vil da fucke ting opp.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Denne tråden var vi ikke ferdig med.)

Det er litt av poenget med constraint, garantere at ingen av dem har samme prio.

Jeg tror dette kan gjøres mye enklere.
Bare bulk flytt på settet du finner.

qs.filter(...).update(prio=F('prio')+1)
qs.filter(...).update(prio=F('prio')-1)

backend/samfundet/views.py Outdated Show resolved Hide resolved
backend/samfundet/views.py Outdated Show resolved Hide resolved
backend/samfundet/views.py Outdated Show resolved Hide resolved
@magsyg magsyg mentioned this pull request Jun 8, 2024
4 tasks
@magsyg magsyg requested a review from emilte June 15, 2024 10:59
Copy link
Member

@robines robines left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ser bra ut!

@magsyg magsyg merged commit 6c4bf71 into master Jun 16, 2024
5 checks passed
@magsyg magsyg deleted the feature/backendpriority branch June 16, 2024 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add backend algorithm for priority
3 participants