ef5396ce65
Status reactions had an API similar to that of announcement reactions, using PUT and DELETE at a single endpoint. I believe that for statuses, it makes more sense to follow the convention of the other interactions and use separate POST endpoints for create and destroy respectively.
25 lines
547 B
Ruby
25 lines
547 B
Ruby
# frozen_string_literal: true
|
|
|
|
class Api::V1::Statuses::ReactionsController < Api::BaseController
|
|
include Authorization
|
|
|
|
before_action -> { doorkeeper_authorize! :write, :'write:favourites' }
|
|
before_action :require_user!
|
|
before_action :set_status
|
|
|
|
def create
|
|
ReactService.new.call(current_account, @status, params[:id])
|
|
render_empty
|
|
end
|
|
|
|
def destroy
|
|
UnreactService.new.call(current_account, @status, params[:id])
|
|
render_empty
|
|
end
|
|
|
|
private
|
|
|
|
def set_status
|
|
@status = Status.find(params[:status_id])
|
|
end
|
|
end
|