Rails%203%20In%20Action

Fixing what you broke
Post, put, delete, and anything
You can define routes that respond only to POST, PUT, and DELETE requests using
the post, put, and delete methods, respectively. All of these methods use the
same syntax and work in similar manners, but they define routes that respond only
to certain HTTP methods.
If it doesn’t matter which HTTP method a route responds to, you can use the match
method:
match '/some_route',
:to => "some#where"
This would respond to GET, POST, PUT and DELETE methods. This method is actually
used by the get, post, put, and delete methods internally, except they call it like this:
match '/some_route',
:to => "some#where",
:conditions => { :method => :get }
You could use conditions to filter the HTTP methods to which a route would respond,
but it’s better to just use the relevant HTTP method’s method.
The get method defines a new route in your application that responds to only GET
requests to /awaiting_confirmation. This route goes to the confirmation action in
UsersController, which you haven’t created yet either. Soon!
The :as option tells Rails that you want routing helpers generated for this route
and you want the helpers to have the prefix confirm_user. This generates
confirm_user_path, which you use in your new check_for_sign_up action in
ProjectsController as well as in a confirm_user_url method.
When you run the Signing Up feature again with bin/cucumber features/signing
_up.feature you don’t get the same error, but you get one that can be easily fixed:
Given I am on the homepage
uninitialized constant UsersController
This is the controller you’ll use to show users the confirmation page, so let’s create it
with a confirmation action that you’ll need with this command:
rails g controller users confirmation
This command adds a route to your routes file that you don’t want (because it overrides
a route that Devise uses), so remove this line from config/routes.rb:
get "users/confirmation"
The added bonus of putting the action here is that you get a view for free at app/
views/users/confirmation.html.erb. In this view you’ll display the “You have signed up
successfully” message as well as a “Please confirm your account before signing in” message.
Before you add these messages to the template, add a line at the bottom of the
scenario inside features/signing_up.feature to check for this confirmation message:
Then I should see "Please confirm your account before signing in."
181