how to give names to rails generated routes?

Question

when using the following on routes.rb: resource :my_model

I get a few automatically generated routes. Some of them have a name (just like when manually defining them with 'as' keyword) but some of them don't.. so how can I give them names? Or maybe it's a 'hint' given to me by rails that I'm not supposed to use these routes?

Can you post your `routes.rb` file and `rake routes` output? I don't think I've ever had a route without a prefix. — Jason, Nov 09 '15 at 13:56
yeah sure, so the routes.rb file includes the following line: resource :global_preferences and here is a screenshot of rake routes result: http://cl.ly/image/0o1e2o0u2Q1i — Ramonsito, Nov 11 '15 at 07:07

score 1 · Answer 1 · answered Nov 09 '15 at 14:52

What do you refer to when you say "name", the Prefix when you run rake routes? Many of the HTTP requests (i.e. patch, put, delete) are handled by the controllers and are intended to then either redirect to another path or alter the DOM of the current page if you're using javascript, so they wouldn't have a prefix associated with them as those requests don't have an associated view.

score 0 · Answer 2 · answered Nov 09 '15 at 14:14

When using a singular resource, all CRUD routes will be generated with the exception of an index route. You do not need names for these paths if you are looking to use them as intended. What is your intent for using these routes?

As per the docs:

A singular resourceful route generates these helpers:

new_resourceName_path returns /re/new
edit_geocoder_path returns /geocoder/edit
geocoder_path returns /geocoder

Please post your output via: bundle exec rake routes You'll notice the show and create controller actions share the same path with the only difference being one expects a POST request and the other a GET request. This is some of the magic provided by Rails allowing you to use similarly named routes that map to different actions.

score 0 · Answer 3 · edited May 23 '17 at 12:03

0

Try resources instead of resource. If you want a helper for PATCH, PUT or DELETE, just use the helper for the show action (that you'll get from resources) and specify the HTTP method with method:.

The second answer here has a decent explanation about your resource call.

edited May 23 '17 at 12:03

Community

1
1

answered Nov 11 '15 at 14:59

Jason

2,725
2
14
22

score 0 · Answer 4 · answered Nov 11 '15 at 15:16

These routes expect a different request method (this implies additional data in request), and do not need separate name, just use generic global_preferences_path and for example - set method for unobtrusive js in link:

<%= link_to 'Set preference', global_preferences_path(some_parameter:'foo'),
        confirm:'Are you sure?', method: :put %>

or use html form or so

how to give names to rails generated routes?

4 Answers4