Rails%203%20In%20Action

Summary
This scenario passes because of the changes you made to the controller and application
layout, where you display all the flash messages. Of course, the third step is now
failing. To display error messages in the view, you need to install the dynamic_form
gem. To install it, add this line to your Gemfile underneath the line for the coffeerails
gem:
gem 'coffee-rails'
gem 'dynamic_form'
Then you must run bundle install to install it. Alternatively, you could install it as a
plugin by using this command:
rails plugin install git://github.com/rails/dynamic_form.git
This command executes a git clone on the URL passed in and creates a new folder
called vendor/plugins/dynamic_form in your application, putting the plugin’s code
inside of it. Installing it as a plugin would lead to a “polluted” repository, so installing
it as a gem is definitely preferred here. Also, when it’s installed as a gem, RubyGems
and Bundler provide an exceptionally easy way of keeping it up to date, whereas the
plugin architecture in Rails doesn’t. This is a good reason to try to use gems instead of
plugins.
The helpful method you’re installing this gem for is the error_messages method
on the FormBuilder object—that is, what f represents when you use form_for in your
app/views/projects/_form.html.erb view:
Directly under this form_for line, on a new line, insert the following to display the
error messages for your object inside the form:
Error messages for the object represented by your form, the @project object, will now
be displayed. When you run rake cucumber:ok, you get this output:
2 scenarios (2 passed)
12 steps (12 passed)
Commit and push, and then you’re done with this story!
git add .
git commit -m "Add validation to ensure names are
specified when creating projects"
git push
3.3 Summary
We first covered how to version-control an application, which is a critical part of the
application development cycle. Without proper version control, you’re liable to lose
valuable work or be unable to roll back to a known working stage. We used Git and
GitHub as examples, but you may use alternatives, such as SVN or Mercurial, if you
prefer. This book covers only Git, because covering everything would result in a multivolume
series, which is difficult to transport.
81