Macro that invokes other macros does not work when imported

[jjkavalam]

Version: github.com/flosch/pongo2/v6 v6.0.0

Background

I have a macro main which i want to use in my templates. To implement this macro, i rely on child macros -child.

{% macro child() %}Child{% endmacro %}

{% macro main() export %}Main calls {{ child() }}{% endmacro %}

What is the issue

main does not work correctly when imported.

How to reproduce ?

1. Create macros.j2 with the contents above.

2. Create test1.j2 with the following contents:

{# filename: test1.j2 #}

{% import "macros.j2" main %}

{{ main() }}

3. Render test1.j2 using the default options. We get the following output:

Main calls 

Expected output:

Main calls Child

Other details (may be useful)

When the macro is called from the same file such as below, we get the expected output:

{# filename: test2.j2 #}

{# macro definition above is pasted here #}

{{ main() }}

[jjkavalam]

#331 contains a working solution

[SharkFourSix]

Bump: Still facing this issue with exactly the same setup as above. In my main macro, I can receive variables fine. The child macro behaves as if it doesn't exist. Even outputing raw text it doesn't write to the client browser.

[enemis]

Also faced with this issue during working with fiber framework. My code is
--form_macros.django

`{% comment %} {% include "lab/components/bootstrap_base_layout.html.twig" %} {% endcomment %}
{% macro form_field(name, label, type="text", value="", error="", required=false) export %}
--- code creates basic text field hypertext
{% endmacro %}

{% macro text_input(name, label, value, error="", required=false) export %}
some text
{{ form_field(name, label, value, error, required) }}

{% endmacro %}`

than i tried used text_input macro in
--login.django
{% import "components/form_macros.django" text_input %} {{ text_input("name", "label", "value") }}

and i got on page only 'some text'

[enemis]

In php twig syntax we used {% import _self as forms %}
to allow use macros in macros but i havent got chance find way to fix this issue in golang properly.

[flosch]

Looking into it, thanks.