How do rails routes work

That's when we use singular term, resource. For example, suppose your application includes these models:.

Join me in a mysterious bug case related to accessibility. This is the final part of the React workshops series created by our team. Let's learn how to This is the third part of the React workshop series created by our team. Let's learn about h Skip to Main Content. If you see something like the above in future, you should understand it. Do not forget the things we talked about above, you will need that knowledge in the next section.

You dig? The root route gets called upon when a request is made to the domain name of your web application depending on the rule you have stated in your routes file.

Now what is the rule? Like we saw above, it means that there is a WelcomesController and an index method action. Here are some other examples:.

You just need to take note of the convention used in naming root routes and you are good to go. There is a shorthand format for naming root routes and it looks like this:. When you generate a new Rails application and point your browser to the root, you will be presented with a root page even though you have not defined a root route.

How is that possible? If you have not seen this give it a shot before you continue reading. Open up your terminal and generate a new Rails application. No, that was not magic : Let me explain what happens. When you have not defined a root for your application, Rails, by default, routes to an internal Rails::WelcomeController and renders a welcome page.

Did that sink in? Rails automatically stops calling this controller Rails::WelcomeController the moment you define a root route in the routes file. Rails allow you to name a route using the :as parameter. Here is one way of doing this:. For example in your views like this:. Should we edit an existing user with whatever data got sent along? The Router is basically just a matching service. The other handy thing that goes on when a request enters your application is that Rails grabs all the parameters that came with it and makes them available for you in a special hash called params that you can later use in your controller.

Lots of training courses and tutorials kind of gloss over routes, and they seem quite easy in hindsight, but I remember learning Rails and getting hung up on what exactly is going on.

Just tell Rails which controller and action to map that route to, and it is so:. From that discussion, they are:. One way to write them out would be the long way:. Two things to notice:. You will be able to access that ID directly from the controller by tapping into the params hash where it got stored. Rails knows you want to use those seven actions all the time… so they came up with a handy helper method which lets you do in one line what we just wrote in seven lines in our resources file:.

That is a Ruby method which basically just outputs those seven routes we talked about before. No magic. You see it a whole lot, now you know what it does. With that above line in my routes file, what do my routes look like? You can see the incoming HTTP verb and URL in the middle columns, then the controller action they map to on the right, which should all be quite familiar because you just wrote it in the routes file.