Building stateless resolver with best practices (#327)

src/Controller/BlogController.php at line 272

/**
 * NOTE: when the controller argument is a Doctrine entity, Symfony makes an
 * automatic database query to fetch it based on the value of the route parameters.
 * The '{slug:post}' configuration tells Symfony to use the 'slug' route
 * parameter in the database query that fetches the entity of the $post argument.
 * This is mostly useful when the route has multiple parameters and the controller
 * also has multiple arguments.
 * See https://symfony.com/doc/current/doctrine.html#automatically-fetching-objects-entityvalueresolver.
 */
#[Route('/posts/{slug:post}', name: 'blog_post', requirements: ['slug' => Requirement::ASCII_SLUG], methods: ['GET'])]
public function postShow(Post $post): Response
{
    // Symfony's 'dump()' function is an improved version of PHP's 'var_dump()' but
    // it's not available in the 'prod' environment to prevent leaking sensitive information.
    // It can be used both in PHP files and Twig templates, but it requires to
    // have enabled the DebugBundle. Uncomment the following line to see it in action:
    //
    // dump($post, $this->getUser(), new \DateTime());
    //
    // The result will be displayed either in the Symfony Profiler or in the stream output.
    // See https://symfony.com/doc/current/profiler.html
    // See https://symfony.com/doc/current/templates.html#the-dump-twig-utilities
    //
    // You can also leverage Symfony's 'dd()' function that dumps and
    // stops the execution

    return $this->render('blog/post_show.html.twig', ['post' => $post]);
}