Heya @JuroOravec, sorry to be a pain but is there a more reliable way to get the slot content without having to render it with self.outer_context, this is proving to be a brittle approach.

Thanks again,
Henk

@HenkWillcock Why is it brittle?

The latest thing that's caused issues is using a {% for %} template loop and passing the value into a slot. E.g:

        {% for item in my_list %}
            {% component "MyComponent" %}
                {{ item }}
            {% endcomponent %}
        {% endfor %}

{{item}} doesn't get rendered with slot(self.outer_context, None, None) because it's not available in self.outer_context, (only my_list is).

There was also another issue around rendering the slot in a secondary function that was called by get_context_data (as opposed to within get_context_data itself), though I resolved that by storing a reference to self.outer_context in get_context_data. The loop issue is the one I can't resolve.

Thank.

Thanks for the details. As you might imagine, the two of us run this project on the side, with very little time on our hands. I'll leave an eventual API improvement to Juro, but meanwhile I want to encourage you to write a PRs that fixes this.

@HenkWillcock Looks like a bug, your example should work. Can you post a full example? What does your MyComponent look like?

Based off of your initial question I am planning to clean up the interaction with slots, so that one could call it by only passing slot data to it (#1096). So the handling of self.outer_context would be done by django-components.

But still, it would practically do the same thing: slot(self.outer_context, None, None).