Rails%203%20In%20Action

Restricting by scope
The :as option on the has_many :permissions association B links your projects to
the thing association on the Permission objects. You need this association defined
here because it’s used by the scope below it.
Usually, you use scope without passing a block (represented by the lambda), but
here the outcome of this scope is dynamic according to which user is passed to it. You
therefore use a block to be able to pass this argument to the method generated by the
scope call, which then becomes available in the block for use in the where statement.
The joins method here joins the permissions table using a SQL INNER JOIN,
allowing you to perform queries on columns from that table too. You do just that with
the where method, specifying a hash that contains the permissions key, which points
to another hash containing the fields you want to search on and their expected values.
This scope then returns all the Project objects containing a related record in the
permissions table that has the action field set to view and the user ID equal to that
of the passed-in user.
With this scope method in place, when you run this spec file again with bin/
rspec spec/controllers/projects_controller_spec.rb, your tests pass because
you’re now scoping down the find in the find_project method. But you still have
one failure:
7 examples, 1 failure
This failing spec is the last one in this file where you assert that users receive the message
“The project you were looking for could not be found” if they attempt to access a
project that is unknown to the system. It fails with this error:
Expected response to be a redirect to
but was a redirect to
Rather than redirecting back to /projects as it should, this code now redirects to the
/users/sign_in path. This would happen only if the user attempted to access an
action that you had locked down to be visible only to those who were signed in.
Recent changes to the show action fit this bill: users are now required to sign in before
you run the find_project method.
Therefore, you just need to make a small fix to this final spec: you must sign in as a
user before you make the get :show request. Let’s change the first two lines of this
spec in spec/controllers/projects_controller.rb from this
it "displays an error for a missing project" do
get :show, :id => "not-here"
to this:
it "displays an error for a missing project" do
sign_in(:user, user)
get :show, :id => "not-here"
Now when you run bin/rspec spec/controllers/projects_controller_spec.rb,
all the examples pass:
171