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

feat: ranking metadata #39

Merged
merged 5 commits into from
Jan 4, 2024
Merged

feat: ranking metadata #39

merged 5 commits into from
Jan 4, 2024

Conversation

tiptenbrink
Copy link
Collaborator

@tiptenbrink tiptenbrink commented Dec 27, 2023

Een aantal nieuwe endpoints voor de nieuwe class update:

  • <server>/admin/class/get_meta/{recent_number}/ (this returns the most recent classifications of each type, recent_number/2 for each type)
  • <server>/admin/class/new/ (creates a new points and training classification)
  • <server>/admin/class/modify/ (modifies a classification)
  • <server>/admin/class/remove/{class_id} (removes classification with id class_id)

Gebruik nu ClassMeta ipv ClassView op nieuwe plekken, laat most_recent_class_of_type nu een lijst returnen van een variabel aantal klassementen (en dan ClassMeta, die alle info heeft). ClassView wordt nog wel op oude plekken gebruikt maar ClassMeta inherit van ClassView dus die werkt nog steeds.

  • Nieuwe update_by_unique database functie.

@tiptenbrink tiptenbrink force-pushed the feat/ranking-metadata branch from ba7bd7e to 6f13757 Compare January 4, 2024 02:48
@tiptenbrink tiptenbrink changed the title DRAFT: feat: ranking metadata feat: ranking metadata Jan 4, 2024
Copy link
Contributor

@lalamiko7 lalamiko7 left a comment

Choose a reason for hiding this comment

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

Looks good!

@tiptenbrink tiptenbrink merged commit 26dd5f2 into main Jan 4, 2024
11 checks passed
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.

2 participants