Twig Params as Twig Path() params
When our current project started we were tasked to create a BaseCrudController. Since we were going to use a lot of basic CRUD actions in the beginning of the project.
Setting up the entire BaseCrudController was not that much of an issue. Except for one small hick-up. When extending this BaseCrudController you would not know what parameter was needed to pass an entity id on to the next view. For example when you wanted to create a view or edit action.
So we were forced to set this parameter name through an abstract function. The endcontroller would look something like the following code example. We’re just displaying the view action here to keep it short and sweet.
If you look at the code you can see we used multiple abstract methods to set-up the endcontroller. In this way we could setup a new CRUD controller fast and with ease. All we had to do was implement the abstracted functions.
For the render in this example we first define the detail view, which is the twig file that should be rendered. The next part is the edit url used in the path so we can navigate to the correct action. The third part is the parameter name for Twig to use in that path. Lastly we would pass the entity itself so it can be displayed in the view.
Our first instinct was to use the twig_param_name in the same way we use any parameter as shown in the next example.
Needles to say, this would throw an error. And so we went on to search for a working solution.
The solution we found was actually very simple. All we had to do was to let Twig know that this was actually a parameter. The way we can do this is by surrounding the twig_param_name parameter with parentheses. This is shown in the next example.
And just like that we had our BaseCrudController figured out with it’s own views and working links.