Don't use the deprecated "_self" variable in Twig templates

[javiereguiluz]

When running tests, I get 4 deprecation notices:

Remaining deprecation notices (4)

Global variable "_self" is deprecated in ? at line 87: 1x
    1x in DefaultControllerTest::testPublicUrls from AppBundle\Tests\Controller

Global variable "_self" is deprecated in ? at line 62: 1x
    1x in DefaultControllerTest::testPublicUrls from AppBundle\Tests\Controller

Global variable "_self" is deprecated in ? at line 28: 1x
    1x in BlogControllerTest::testIndex from AppBundle\Tests\Controller

Global variable "_self" is deprecated in ? at line 57: 1x
    1x in BlogControllerTest::testAdministratorUsersCanAccessToTheBackend from AppBundle\Tests\Controller\Admin

The reason is that our templates use this code:

{{ show_source_code(_self) }}

The _self variable is deprecated and it will be removed in Twig 2.0. We need to replace it by:

{{ show_source_code() }}

But then, inside the Twig extension I don't know how to get the name or path or code of the template that called the show_source_code() function.

[xabbuh]

Can't you pass current instead of _self?

[javiereguiluz]

I don't understand you. Like this?

{{ show_source_code(current) }}

[xabbuh]

yes

[javiereguiluz]

I still don't understand 😞 The current variable doesn't exist anywhere.

[xabbuh]

Hm, seems that you can use current only for macros.

[javiereguiluz]

Somewhat related to this, I have the following in a Symfony application:

{% form_theme form _self %}

What would be the equivalent now that _self is deprecated?

[stof]

@javiereguiluz I will try to find a way to refactor the display of the source code to avoid relying on _self. but it will wait until this evening

[voronkovich]

I think we could just replace the _self instances in the templates by actual files names, like this:

{{ show_source_code('blog/edit.html.twig') }}
...
{{ show_source_code('@XyzBundle/x/y/z.html.twig') }}
...
{% form_theme form 'admin/blog/edit.htm.twig' %}

[javiereguiluz]

@voronkovich yes, but that would be SO boring!! Let's wait for the solution that will propose @stof. In any case, there is no need to hurry. This variable won't stop working until Symfony 3.0.