Rails%203%20In%20Action

Summary
Great! With the ability to delete users implemented, you’ve completed the CRUD for
Admin::UsersController and for the users resource entirely. Now make sure you
haven’t broken anything by running rake cucumber:ok spec. You should see this
output:
33 scenarios (33 passed)
286 steps (286 passed)
# and
14 examples, 0 failures, 7 pending
Fantastic! Commit and push that:
git add .
git commit -m "Added feature for deleting users,
including protection against self-deletion"
With this final commit, you’ve got your admin section created, and it provides a great
CRUD interface for users in this system so that admins can modify their details when
necessary.
7.9 Summary
For this chapter, you dove into basic access control and added a field called admin to
the users table. You used admin to allow and restrict access to a namespaced controller.
Then you wrote the CRUD interface for the users resource underneath the admin
namespace. This interface is used in the next chapter to expand on the authorization
that you’ve implemented so far: restricting users, whether admin users or not, to certain
actions on certain projects. You rounded out the chapter by not allowing users to
delete themselves.
The next chapter focuses on enhancing the basic permission system you’ve implemented
so far, introducing a gem called cancan. With this permission system, you’ll
have much more fine-grained control over what users of your application can and
can’t do to projects and tickets.
163