Rails%203%20In%20Action

Writing your first engine feature
"forem/posts/form", :locals =>
➥{ :post => post} %>
Alright now, with the action, the view, and the form partial defined, you’re almost
there. In this partial though, you reference another partial called forem/posts/
form B, passing through the local variable of the post form builder object as f to it
by using the :locals option. You’re using the long form here, as Rails cannot infer
the name of it any other way.
This new partial will provide the text field that you’ll use for posts. You’re placing it
into a partial because you may use it later on if you ever create a form for creating new
posts, like a reply feature for a topic.
Let’s create the file for this partial now at app/views/forem/posts/_form.html.erb
and put these lines in it:
Even though this is an extremely short partial, it’s good to separate it out so that it can
be shared across the topic and posts forms, and also in case you ever decide to add any
additional information to a post.
Your test should get a little further when you run bin/rspec spec/integration/
topics_spec.rb again:
AbstractController::ActionNotFound:
The action 'create' could not be found for Forem::TopicsController
Now you need to define the create action, the second to last action along this chain,
with the show action being the last.
17.5.6 The create action
The create action will take the parameters passed from the form provided by the new
action and create a new Topic object with a nested Post object. This action should set
the flash[:notice] variable to inform the user that the topic could be created and
then redirect to the show action.
This action needs to be defined using the code shown in the following listing, placing
it under the new action.
Listing 17.7 app/controllers/forem/topics_controller.rb
def create
@topic = Forem::Topic.create(params[:topic])
flash[:notice] = "Topic has been created!"
redirect_to @topic
end
B
Reference
partial
489