Fixes to API access endpoint and update some exposed properties #3038
Conversation
This file contains hidden or 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
…point Include also the endpoints accounts and clarifications that were missing.
eldering
force-pushed
the
fix-api-access-endpoint
branch
3 times, most recently
from
df213af to
080f83c
Compare
|
I already had a local change for |
|
I can also remove |
Sure that would work indeed |
Don't exactly check for each property as that's just silly repeating of lists.
eldering
force-pushed
the
fix-api-access-endpoint
branch
from
080f83c to
9992568
Compare
Done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
List all properties (also DOMjudge specific ones) in the access API endpoint, and add endpoints
accountsandclarificationsthere.Also remove exposing
problems.types_to_stringand addjudgements.current(as alias ofvalid).