Steps

Step 1: Add the edit page

Say we want to edit the first job posting. If we look at http://localhost:3000/rails/info, we see this line:

edit_job_path         GET   /jobs/:id/edit(.:format)   jobs#edit

So, it looks like if we want to edit the job description, we should visit this URL: http://localhost:3000/jobs/1/edit.

Error! Woo!!!

The action 'edit' could not be found for JobsController

what would be the next step?

Step 2: add the edit action to the JobsController

Let's add the controller action above the word private:

def edit
  @job = Job.find(params[:id])
end

Discussion: Params

---

What is Job.find(params[:id]) doing? What is params again?

Refresh http://localhost:3000/jobs/1/edit

Error! Woo!!!

JobsController#edit is missing a template for request formats: text/html

what would you do next?

Step 3: add a view

Alright, let's add that edit view, under app/views/jobs/edit.html.erb

<h1>Edit Posting</h1>

Refresh http://localhost:3000/jobs/1/edit

There should be no more errors

Step 4: plan the update form

Okay, so that's awesome. Now we just have to add a form for editing. I wonder if it is any different from the create form? I guess we could copy and paste the other form?

We could copy and paste from the other form, but we try to avoid that because duplicated code is hard to maintain. For example, if I want to add placeholder text for the inputs in the form, when the code is duplicated, I’ll need to update the code in each place the form was copied. (In large apps it’s easy to miss a place that would need to be updated.) The solution is to reuse rather than duplicate the code, and the way to reuse code in views is by using partials.

Discussion: Don't Repeat Yourself (DRY)

---

DRY is an important principle in rails. So much so that we use DRY as a verb:

• What are some reasons to DRY up our code?
• What are some strategies for DRYing up code throughout a Rails app?

Step 5: create a partial for the form

Rails form helpers are designed beautifully for CRUD interfaces. So we're not gonna have to write very much code to make this form work for editing AND creating job postings.

But first, a refactor: we're going to move the create form into a partial.

Refactoring is improving code while maintaining the behavior it produces. It's an important part of software development.

Make a new file under jobs like so: app/views/jobs/_form.html.erb, and move the following code OUT of app/views/jobs/new.html.erb and into the _form.html.erb file:

<%= form_with(model: @job, local: true) do |form| %>
  <div>
    <%= form.label :title %>
    <%= form.text_field :title %>
  </div>

  <div>
    <%= form.label :description %>
    <%= form.text_area :description, size: '60x6' %>
  </div>

  <div>
    <%= form.submit %>
  </div>
<% end %>

Now, in app/views/jobs/new.html.erb, add the following line:

<%= render "form" %>

Add a job posting with http://localhost:3000/jobs/new, just to make sure that the form is working as expected.

Step 6: re-use the partial

Now that we have a form partial, we can reuse it! In app/views/jobs/edit.html.erb, we can add the same line under the header:

<%= render "form" %>

Refresh the page http://localhost:3000/jobs/1/edit

It now shows the data from the job it loaded from the database. Good.

Step 7: Actually Update The Job

Let's try to update that job posting. Change something about the job posting, and submit the form.

Error! Woo!!!

The action 'update' could not be found for JobsController

So it looks like the form is finding the right route, but the method is missing from the controller.

Step 8: Add the update action to the JobsController

Let's add the update method--again, above the word private--to the file jobs_controller.rb

def update
end

Try it again, and ... no output. In the logfile you will find a 'no template found' error. Similarly to create, we don't want a template to render for update. So let's just send them back to the jobs listing.

def update
  redirect_to jobs_path
end

Try again, and ... no errors! But we're still not seeing our changes.

Discussion: What is this controller method missing?

---

Who knows what we're missing?

Take a look at the create method on the jobs controller.

(Spoilers below, so don't keep scrolling!)

• here
• is
• some
• strategic
• white
• space
• so
• the
• answer
• isn't
• immediately
• visible!

Here's what the update method should actually look like:

def update
  @job = Job.find(params[:id])
  @job.update(job_params)
  redirect_to jobs_path
end

We needed to save our changes to the database so they can actually persist! If you didn't have the discussion before and work out the answer, go through this method line-by-line explaining precisely what the code is doing.

Step 9: Add a Link

Our users probably aren't going to know they can hit /jobs/:id/edit to visit the edit form, so let's add a link so it's easy to find!

In app/views/jobs/index.html.erb, just add this line with the <h5> header in it ... don't copy and paste the whole thing!

<% @jobs.each do |job| %>
  <h3><%= job.title %></h3>
  <p><%= job.description %></p>
  <h5><%= link_to "Edit Posting", edit_job_path(job)%></h5>
<% end %>