Controller Magic: Param Conversion

Hey Mike,

I'm glad you found the solution by yourself, well done! Solution sounds easy, or you can always write custom queries inside your controller/action to find proper objects instead of doing it via param converter, it always works for complex tasks and easier to do ;)

Cheers!

I think I've found the answer myself :)
https://stackoverflow.com/a...

UPDATE://
This works:

* @Entity("category", class="App\Entity\Category", options={
* "repository_method" = "findAllBySlug",
* })

But it throws a deprecation, that repository_method will be unavailable in sf 6.
But if I use instead this code:

* @Entity("category", expr="repository.findAllBySlug(slug)")

Or this:

* @Entity("category", expr="category.findAllBySlug(slug)")

nothing happens.
(SF doesn't event go into my findAllBySlug method)

Update2://
Final Code:
composer require symfony/expression-language

* @Entity("category", class="App\Entity\Category", expr="repository.findAllBySlug(slug)")

I find it a bit disappointing, that I need to install another service for (deprecated) built in methods.
Because I can measure a nagative speed impact (approx. -5 ms) on other sites where I don't use @Entity.
I haven't had that negative speed impact with the built in repository_method option.

Anyway I'am thankful that SF provides a clean solution :)

Is it possible to access multiple entitys through a single @Route annotation?
By example with this param conversion?

I want to achieve something like: /search/$term/categorie1,categorie2
Which should show all articles with the word $term and which are in categorie1 and categorie2

At the moment SF only has access to one category entity via:
* @Route("/search/{term}/{category}/{page}", name="app_search")

Hey Ahmedbhs!

Yes, you're correct: if the Genus is not found, then a NotFoundHttpException is thrown, which will cause a 404 page. You can customize the 404 page (there are docs on this - it's pretty simple), but there will not be any simple way to know when you're customizing it what caused the 404. So, it's easy to have one 404 page for your site. But, if you want a different 404 error for difference sections of you're site, you'll need to do a bit more work, unfortunately:

1) Do not use the ParamConverter
2) Create a new Exception class that extends NotFoundHttpException - e.g. CustomMessageNotFoundHttpException - something like:

class CustomMessageNotFoundHttpException
{
    public function __construct(string $message = null, \Exception $previous = null, int $code = 0, array $headers = array())
    {
        parent::__construct($message, $previous, $headers, $code);
    }

    public function getCustomMessage()
    {
        return $this->getMessage();
    }
}

3) Manually query for the Genus and throw this exception if it's not found - use whatever message you want
4) When you create your custom 404 template - https://symfony.com/doc/cur... - your template will be passed an exception variable. You can use it to see if your exception has a custom message or not:

{% if exception.customMessage is defined %}
    {{ exception.customMessage }}
{% endfor %}

Yes, this is a bit of work - it could definitely be easier in Symfony. One alternative is to (A) NOT use the param converter, (B) check for the Genus in your class and then (C) just render some custom error template from right inside your controller. That is probably a fine solution. However, by NOT throwing an exception, you may lose some minor things, most notably, you won't see the 404 in your logs. That might not be a huge deal - just be aware that Symfony wants you to throw an exception for a 404, so if you just render your own template from a controller, you're working around some of the things that it wants to do.

Cheers!

If the identifier of an Genus does not necessarily exist then the paramConvertor will trigger an exception. Is it sensible to treat this exception or not ? If you want to send a simple message to the user showing that this category does not exist.

THAT IS AWESOME! I was looking everywhere for this "requirements=" to keep it DRY!
Thanks loads
Always find great answers here!

Hey James Davison!

Ah! So basically, you have a Url entity, which allows you to define 100% custom URLs, and when you go to a specific URL, it will then display the page/product/category (whatever "thing" is related to that URL object). Here is what I would do:

/**
 * The requirements= part allows the URL key to contain "/" and still match this route - https://symfony.com/doc/current/routing/slash_in_parameter.html
 *
 * @Route("/{key}, name="app_url_show", requirements={"key"=".+"})
 */
public function showPage(Url $url)
{
    // getPageType() would return one of these constants, depending on what type of object it's related to
    switch ($url->getPageType()) {
        // Create 3 constants for convenience - e.g. const PAGE = 'page';
        Url::PAGE:
            // create 3 separate functions that each render the page type
            // if you also need the Url object, pass that as a second argument
            return $this->renderPage($url->getPage());
        Url::PRODUCT
            return $this->renderProduct($url->getProduct());
        Url::CATEGORY
            return $this->renderCategory($url->getCategory());
        default:
            throw new \Exception('Invalid page type');
    }
}

Let me know if that makes sense :).

Cheers!

Hey Ryan,

Maybe it is more complex than it needs to be. I am trying to create an entity URL to have only unique URL. Then I link this URL to specific page/product/category. Does it make sense to do it that way?

Hey James!

Ah, excellent question. So actually, no. By the time the param converter is called, Symfony has determined that *this* route *has* matches the URL. And so, if the param converter fails, it will be a 404 - it will *not* continue and try to match the next route. I don’t know the full situation, but my recommendation (because your setup is a bit complex) is to skip the param converter and put the logic in your controller. But, you can organize things nicely. For example, if you find the Page, you can then call some private function to do the work for rendering that page - e.g. return $this->renderPage($page);. If you did not find the page, query for the Category and then call some other function that renders the category. It should keep things nicely organized.

Let’s me know how it all works! Cheers!

Hi Ryan,

Just to be sure I understand. If I do the same for my product controller and category controller, Symfony will first look for an url related to page, if does not find will move on the next possible match ...

Thanks

Hi Ryan,

Thanks for taking the time to answer me.

I have created an innerJoin as below, I will let you know if it works.

public function findUrl($urlKey)
{
return $this->createQueryBuilder('page')
->andWhere('url.key LIKE :searchTerm')
->innerJoin('page.url', 'url')
->setParameter('searchTerm', $urlKey)
->getQuery()
->execute();
}

Thanks again

Hey James Davison!

Hmm, interesting! Does the second option work? I actually don't know if it does immediately because, in general, if I have a situation that seems too complex for the ParamConverter, I just skip it :). Instead I add the few extra lines at the top of my method to query manually - it's not much more work, and it's very clear.

But, in general, I think your approach should work. Except that you will probably need a join in your repository method because it looks like you actually have a Url entity that needs the WHERE clause. So, you would probably need to create a custom query builder, innerJoin over to this Url entity, and add the andWhere on its key property. Here is some info about those types of queries: https://symfonycasts.com/sc...

Let me know if that helps! Cheers!

Would this be a possible solution:

Repository
class PageRepository extends EntityRepository
{
public function findUrl($urlKey)
{
return $this->findBy(array(), array('url' => $urlKey));
}
}

Controller
/**
* @Route("/{url}.html", name="show_page")
* @Entity("page", expr="repository.findUrl(url)")
*/
public function showPageAction(Page $page, Request $request)
{
// return a page if it exist or go to next route available
}

Hi guys,

I am trying to use the Param Converter. Is there a way to find a result from a joint relation?

I have created an Entity called URL which is connected to Page.

Code below:
/**
* @Route("/{url}.html", name="show_page")
* @ParamConverter("url", options={"mapping"={"url"="url.key"}})
*/
public function showPageAction(Page $page, $request)
{
// return a page
}

Is it something which is possible?

Thanks

James

Thanks for the quick and detailed reply.
That's very useful.

Hey Nina,

"git grep genus_show_notes" command will work if you have committed changes about "genus_show_notes" route. If you add this route but do not commit yet - it won't work, because this command search in the current repo state, i.e. only changes you committed. You can use PhpStorm's "Find in path" feature (Edit -> Find -> Find in path) to search for uncommitted changes in your project or commit them and use "git grep".

Or you can use Symfony Console command:
$ bin/console debug:router genus_show_notes

to see the full information about genus_show_notes route in your app.

Cheers!

Hello, please help me.
I go to the terminal and search for the route name
use command :
git grep genus_show_notes

but see nothing just go to the next line
Why? And how to fix this? How to find links on this route ("genus_show_notes")?

Hey maxii123 ,

Yeah :) Anyway, it's just a quick start. Of course, if you have more complex logic - you can do it manually, but it saves you time because probably you need a complex logic not always. And btw, even if you have more complex logic - you can write your custom param converter and still continue using this magic ;)

Cheers!

The param matching is all well and good but god knows I wouldnt want to maintain this stuff down the road ;)

Hey Nefi,

Hm, you can try to add "\" before like "\dump($genus)" - I hope it helps. But it depends, please, take a look at this explanation: http://stackoverflow.com/a/...

Cheers!

dump($genus) don't work for me in the controller generates the next error, Attempted to call function "dump" from namespace "AppBundle\Controller". :(

Hey Andrew!

The code is up now - you were working ahead of us :). Sometimes a few of the tutorials are "secretly" available for a few days before we actually put the code blocks up.

Cheers!

No code is bad news for me. It's difficult to follow.