This repository was archived by the owner on Dec 20, 2023. It is now read-only.
More klassement routes: user per event, events per class and events per user #66
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This contains three new routes:
/admin/class/events/user/{user_id}/is for getting all events of a user in a specific class, which can be given explicitly or just referred to as "points" or "training"/admin/class/events/returns all events in a class. Again either by explicitly giving the class id or ranking type./admin/class/events/{event_id}/gets all users and their points for a specific event, using only the event_id.There was also some wrong syntax in the aggregation query, which e.g. affected
/admin/class/sync/(previously/admin/classification/sync/{publish}/). This has now been fixed.The only routes left are for modifying stuff. For modifying/adding a user to an event we already have a data function, but not yet a route.