This repository has been archived by the owner on Dec 16, 2024. It is now read-only.
Add User in Event Endpoint #50
Merged
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
It involved a bit of fixing in the Availability from_sql() function, but it works well enough.
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.
What?
Adds the
/user_in_eventendpoint, which returns a user's availability if they have added theirs to the specified event. The format of data to send is as follows:Why?
We need a way to check if a user has availability to edit, and what info to pre-populate the grid with.
How?
The same as I've been doing every other endpoint, though it required some fixing of the Availability class functions.
Testing?
I tested both scenarios, with users being in and out of events. Seems to work just fine, using already-implemented methods that have been working for other endpoints.