24099e880b
We were rendering the `new` action, but that action doesn't exist.
Before commit ec861ca8e, we were rendering the `edit` action of an
answer, which was confusing as well.
Note that, when adding an invalid document, `@answer.documents` contains
that invalid document (which is not present in the database). Since
we're rendering the index, this new document would appear in the list of
the documents that can be deleted; to avoid that, we're kind of
"reloading" the answer object in the component by finding the record in
the database. We aren't using `@answer.reload` because doing so would
remove the validation errors.
31 lines
676 B
Ruby
31 lines
676 B
Ruby
class Admin::Poll::Questions::Answers::DocumentsController < Admin::Poll::BaseController
|
|
include DocumentAttributes
|
|
|
|
load_and_authorize_resource :answer, class: "::Poll::Question::Answer"
|
|
|
|
def index
|
|
end
|
|
|
|
def create
|
|
@answer.attributes = documents_params
|
|
authorize! :update, @answer
|
|
|
|
if @answer.save
|
|
redirect_to admin_answer_documents_path(@answer),
|
|
notice: t("admin.documents.create.success_notice")
|
|
else
|
|
render :index
|
|
end
|
|
end
|
|
|
|
private
|
|
|
|
def documents_params
|
|
params.require(:poll_question_answer).permit(allowed_params)
|
|
end
|
|
|
|
def allowed_params
|
|
[documents_attributes: document_attributes]
|
|
end
|
|
end
|