Rails%203%20In%20Action

160 CHAPTER 7 Basic access control
flash[:notice] = "User has been updated."
redirect_to admin_users_path
else
flash[:alert] = "User has not been updated."
render :action => "edit"
end
end
When you run bin/cucumber features/editing_users.feature again, the first and
third scenarios pass, but the second one fails because you haven’t set the user’s admin
capabilities inside the update action, as you did in the create action. To do so,
remove the following line from the create action:
@user.admin = params[:user][:admin] == "1"
Now define a method called set_admin, which you can use in both actions. This
method goes directly underneath find_user under the private keyword, as shown in
the following listing.
Listing 7.30 app/controllers/admin/users_controller.rb
private
def set_admin
@user.admin = params[:user][:admin] == "1"
end
To use this method in the update action, place it directly above the call to update
_attributes:
set_admin
if @user.update_attributes(params[:user])
Placing set_admin above update_attributes ensures that the user is made an admin
directly before the save for update_attributes is triggered. You should also put it
before the save in the create action:
set_admin
if @user.save(params[:user])
Now when you run the feature, all the scenarios pass:
3 scenarios (3 passed)
41 steps (41 passed)
In this section, you added two more actions to your Admin::UsersController: edit
and update. Admin users can now update users’ details if they please.
Run rake cucumber:ok spec to ensure nothing was broken by your latest changes.
You should see this output:
31 scenarios (31 passed)
270 steps (270 passed)
# and
14 examples, 0 failures, 7 pending