-
Notifications
You must be signed in to change notification settings - Fork 11
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
Reverse Actions #50
Milestone
Comments
cf7
pushed a commit
that referenced
this issue
Dec 9, 2016
cf7
pushed a commit
that referenced
this issue
Dec 10, 2016
SirSeim
added a commit
that referenced
this issue
Dec 11, 2016
DELETE `/api/dropins/{dropinID}/checkin` example payload: ```json { "clients": [ 2,3,4 ] } ```
SirSeim
added a commit
that referenced
this issue
Dec 11, 2016
To checkout a client from a dropin: {
"clients": [
2,3,4
]
} Returns: {
"statusCode": 200,
"message": "Success checking out client from dropin!",
"result": {
"dropin": 2,
"clients": [
2,
3,
4
]
}
} If client IDs are not being returned, its most likely because that client is not associated with that dropin (aka, you never checked in that client for that dropin) |
Files is completed |
So isn't this complete? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For every action that SPY staff can utilize on the app, there needs to be another action that reverses it . . .
(This does not mean that every button needs an undo button right next to it.)
It means doing things such as the following . . .
The text was updated successfully, but these errors were encountered: