Menu
In Rails 3 Match used to point to an action for both "GET" and "POST" and other type of requests.
match "user/account" => user#account Now this will point to account action of user's controller for both GET and POST requests. As in Rails 4 "match" has been deprecated, can we create same route for GET and POST in Rails 4?
683
Rails routes are matched in the order they are specified, so if you have a resources :photos above a get 'photos/poll' the show action's route for the resources line will be matched before the get line. To fix this, move the get line above the resources line so that it is matched first.
Rails RESTful Design which creates seven routes all mapping to the user controller. Rails also allows you to define multiple resources in one line.
A member route will require an ID, because it acts on a member. A collection route doesn't because it acts on a collection of objects. Preview is an example of a member route, because it acts on (and displays) a single object.
From the match documentation, you can use match as long as you have via:
match "user/account" => "user#account", as: :user_account, via: [:get, :post] Edit: Added a as: parameter so that it will be accessible via a url helper. user_account_path or user_account_url in this case.
160
On routes, the match method will no longer act as a catch-all option. You should now specify which HTTP verb to respond to with the option :via
match "/users/:id" => "users#show" match "/users/:id" => "users#show", via: :get match "/users" => "users#index", via: [:get, :post] Another option for better Rails 3.2 compatibility is to just specify your actions with explicit get, post, or any other HTTP verb. With this option, you still get your code running today and future proof it for the upgrade.
get "/users/:id" => "users#show" get "/users" => "users#index" post "/users" => "users#index" If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
