Rails%203%20In%20Action

Linking tickets to users
Then I should see "You need to sign in or sign up before continuing."
When I fill in "Email" with "user@ticketee.com"
And I fill in "Password" with "password"
And I press "Sign in"
Then I should see "New Ticket"
The step that checks for the text “You need to sign in or sign up before continuing”
fails because you’re not ensuring the user is signed in before the new action in the
TicketsController.
To do so, you can use the Devise-provided method authenticate_user! as a
before_filter. Put this method directly underneath the class definition for Tickets-
Controller inside app/controllers/tickets_controller.rb. The placement of this
before_filter ensures that if it fails, the other two before_filters underneath it
will not needlessly run, eventually saving valuable CPU cycles.
The line you put in the TicketsController is
before_filter :authenticate_user!, :except => [:index, :show]
This line ensures that users are authenticated before they go to any action in the controller
that isn’t the index or show, including the new and create actions.
By ensuring this authentication, you’ll know which user created a ticket during the
creation process, so let’s link tickets to users.
6.5.1 Attributing tickets to users
To link tickets to specific users, you alter the build line in your create action in
TicketsController from this line
@ticket = @project.tickets.build(params[:ticket])
to this:
@ticket = @project.tickets.build(params[:ticket].merge!(:user => current_user))
The merge! method here is a Hash and HashWithIndifferentAccess method, which
merges the provided keys into the hash and overrides any keys already specified. 2
When you run the feature again using bin/cucumber features/creating_tickets
.feature, it complains about an unknown attribute in all three scenarios:
unknown attribute: user (ActiveRecord::UnknownAttributeError)
This error occurs because you haven’t added a belongs_to association between the
Ticket and User. Let’s open app/models/ticket.rb and add this line directly under the
belongs_to :project line:
belongs_to :user
The belongs_to method defines methods for accessing the association, as has_many
does, except here you retrieve only one record. Active Record knows which record
to retrieve when you call either project or user on a Ticket object because it
2 Which could happen if someone hacked the form and attempted to pass their own user attribute.
129