Rails%203%20In%20Action

222 CHAPTER 9 File uploading
asset field to use the assets method, because it’ll need to check the assets of a ticket
rather than the asset. You also need to change the h3 that currently reads Attached
File so it reads Attached Files because there’s more than one file. You should also
change the div that encapsulates your assets to have the class attribute of assets.
These three changes mean that you now have these three lines in app/views/tickets/
show.html.erb:
Attached Files
When you call exists? this time, it calls the ActiveRecord::Base association method,
which checks if there are any assets on a ticket and returns true if there are. Although
assets isn’t yet defined, you can probably guess what you’re about to do.
First, though, you need to change the lines underneath the ones you just changed
to the following:
Here you switch to using the assets method and iterate through each element in the
array, rendering the same output as you did when you had a single asset.
All of these changes combined will help your scenario pass, which is a great thing.
When you run this scenario again, the first file field step passes, but the second fails:
And I attach the file "spec/fixtures/speed.txt" to "File #1"
And I attach the file "spec/fixtures/spin.txt" to "File #2"
cannot attach file, no file field with id, name,
or label 'File #2' found (Capybara::ElementNotFound)
You could add another field:
But that’s a messy way of going about it. The best way to handle this problem is
through an associated model, a has_many association, and by using nested attributes. To
use nested attributes in the view, you use the fields_for helper. This helper defines
the fields for an association’s records, as many as you like. Let’s remove the file field
completely and replace it with this:
B Number increment