Skip to content

Add support for Push Stacks #304

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
hyperNURb wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Add support for Push Stacks #304

hyperNURb wants to merge 4 commits into from

Conversation

@hyperNURb
Copy link
Contributor

@hyperNURb hyperNURb commented Oct 1, 2025

Took a stab at implementing the push/stack feature discussed in #183 to enable components to inject content (scripts, styles, metadata).

What's New

  • <c-stack name="..."> - Declares a stack location where content will be rendered
  • <c-push to="..."> - Pushes content to a named stack from anywhere in the template
  • Automatic deduplication - Prevents duplicate content when components are used multiple times
  • Optional middleware - CottonStackMiddleware for post-render processing
  • Flexible control - multiple flag, custom key/id for deduplication

Example

<!-- base.html -->
<html>
  <head>
    <c-stack name="head" />
  </head>
  <body>...</body>
</html>

<!-- tooltip.html -->
<div class="tooltip">{{ slot }}</div>

<c-push to="head">
  <script src="{% static 'js/tooltip.js' %}"></script>
</c-push>

Feedback appreciated! 🙏

@hyperNURb hyperNURb changed the title Push Stacks Add support for Push Stacks Oct 1, 2025
@wrabit
Copy link
Owner

wrabit commented Oct 7, 2025

Hi - thanks for the PR.. I also have a branch for this which is quite complete and for sure will have some overlap with yours, I also reflect on the sub thread here regarding using a single portal tag with attrs (name|to) and unique attribute. I will plan some time soon to review it and take it forward and will be checking your branch for anything I missed.. 👍

@hyperNURb
Copy link
Contributor Author

hyperNURb commented Oct 7, 2025

@wrabit Want me to update this PR per the sub-thread, or would you rather move ahead with your branch? Either works for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@hyperNURb @wrabit