Skip to content

Conversation

@natboehm
Copy link
Contributor

This implements deployable chunk 3: declining invitations of issue #924. The api route for declining an invite is the same as for accepting an invite. To know that an invite is being declined instead of accepted, the accepted field passed to the backend is set to false. If declined, the invite should be replaced with a message to the user confirming that they declined the invitation for the crate.

former version used two separate routes for accept and decline, now
use one route but have boolean value sent back indicating if invite
was accepted or declined
…es of the crate_id, want crate_id for corresponding user_id
crate_owner_invitation: InvitationResponse,
}
Ok(req.json(&R { crate_owner_invitation: crate_invite }))
decline_invite(req, conn, crate_invite)
Copy link
Member

Choose a reason for hiding this comment

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

I really like how this ended up, the code's easier to read and well organized! 💯

@carols10cents
Copy link
Member

bors: r+

bors-voyager bot added a commit that referenced this pull request Sep 25, 2017
1085: Decline owner invites r=carols10cents

This implements deployable chunk 3: declining invitations of issue #924. The api route for declining an invite is the same as for accepting an invite. To know that an invite is being declined instead of accepted, the `accepted` field passed to the backend is set to `false`. If declined, the invite should be replaced with a message to the user confirming that they declined the invitation for the crate.
@bors-voyager
Copy link
Contributor

bors-voyager bot commented Sep 25, 2017

Build succeeded

@bors-voyager bors-voyager bot merged commit 3d7a851 into rust-lang:master Sep 25, 2017
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