Rails%203%20In%20Action

Attaching many files
TicketsController’s new action, however, you don’t initialize any assets for this ticket,
so assets returns an empty array and no fields at all are displayed.
To get this action to render three file input fields, you must initialize three Asset
objects associated to the Ticket object the form uses. Change your new action inside
TicketsController to this:
def new
@ticket = @project.tickets.build
3.times { @ticket.assets.build }
end
The final line of this action calls @ticket.assets.build three times, which creates
the three Asset objects you need for your fields_for.
When you run the scenario again, the three fields are available, but the scenario
now fails because it can’t find a file to upload:
And I attach the file "spec/fixtures/speed.txt" to "File #1"
And I attach the file "spec/fixtures/spin.txt" to "File #2"
And I attach the file "spec/fixtures/gradient.txt" to "File #3"
And I press "Create Ticket"
/home/you/ticketee/spec/fixtures/
spin.txt file does not exist (RuntimeError)
Create this spin.txt file now inside the spec/fixtures directory, and give it the following
content:
Spinning blink tags have a 200% higher click rate!
You also need to add the gradient.txt file to the same directory, and it contains this:
Everything looks better with a gradient!
These two text pieces are random filler meant only to provide some text if you ever
need to reference it. Let’s run the scenario again:
And I press "Create Ticket"
unknown attribute: asset (ActiveRecord::UnknownAttributeError)
You got this message earlier when you were implementing single-file uploading
because you didn’t define has_attached_file on the Ticket class. Let’s get more
backtrace for this error by using the -b switch at the end of the command: bin/cucumber
features/creating_tickets.feature:36 -b. This command provides the whole
backtrace for an error. In this particular backtrace, you’re after anything to do with
assets, because that’s the only thing that’s changed since this feature was passing. You
should see a line like the following about 10 lines down:
.../active_record/nested_attributes.rb:254:in 'assets_attributes='
This line indicates that the failure most likely has to do with the assets_attributes=
method, which was kindly enough provided by Rails through the call to
accepts_nested_attributes_for. If this error occurs after the assets_attributes=
method, then it definitely has to do with this method. In fact, it’s probably because
225