All language subtitles for 6.refactoring-the-blog-post-routes

Now let's move the existing post route handlers to the PostController.

These two routes are already defined within the resource routes, so all we

need to move are the callback functions. Copy the contents of these

functions to the appropriate PostController actions.

The create action just needs to render the create template.

The store action validates the input from the injected request

object and redirects the user back to the form.

The great thing is we can leave all of this code as it is.

We don't need to change anything.

This route will still work because the route name provided by

the resource method is still posts.create.

If you want to make sure of that,

you can again run the artisan command for listing all of the

routes and their respective names. And that's it.

The transition was really easy because we already used all of the best naming

practices. In the next module, we will start implementing the rest of the

controller actions, and we will also actually store the post to the database

instead of just having this flash message.