Voting endpoints should be more REST-like #5
Description
Right now there are three main voting endpoints:
Vote to accept: /bhap/{id}/vote-accept
Vote to reject: /bhap/{id}/vote-reject
Delete a vote: /bhap/{id}/delete-vote
Gross. What was I thinking? Instead there should be one endpoint. Accepts and rejects should send POSTs and have their accept/reject value in the body. A DELETE request will delete the vote.