Rails%203%20In%20Action

202 CHAPTER 8 More authorization
Listing 8.16 app/views/admin/permissions/index.html.erb
Permissions for
:put do %>
Project
This template defines the table discussed earlier. It provides a header row of permission
titles and rows for each project containing that project’s name followed by check
boxes for each of the permissions. In this view, you use the form_tag, which generates
a form that points to the path specified by its first argument. You also use a
permissions helper method B, which isn’t currently defined but will provide a list of
permissions to iterate through to check on each project.
Right underneath where you use permissions, you use another helper method
called cycle B. This method is built into Rails and cycles through its given arguments
for each iteration of whatever it’s encapsulated in, so when this page displays the first
project, the method sets the class of that tr tag to odd and the second one to even. It
cycles between these two classes until it runs out of projects. This is how you can easily
get different rows in this table to be styled differently.
Before we look at how to define the permissions method, run bin/cucumber
cucumber features/assigning_permissions.feature:
undefined local variable or method
'update_user_permissions_path' [...]
You get an error because you haven’t yet defined the route for the form. The
Admin::PermissionsController serves a different purpose than the standard REST
controllers. For this controller, you use the update action to update a whole slew of
permissions rather than a single one. To map to this action by using the update
B
C