-
Notifications
You must be signed in to change notification settings - Fork 37
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.
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
Feature request: Transparently pass request object to components if present #45
Comments
Yes please! And if possible add a flag in settings, that will allow passing all context from the parent component to the component? So people can choose if they want to have parent context passing or not. |
that would be nice, I'm passing long arguments in my components now and it becomes ugly. example: |
I would love that, I'm grinding my brain to find a workaround on a related problem, as I'm running slippers with htmx for a couple months, we're now struggling on passing many parameters and using them. Right now this is the the Button component we have (with lots of improvements like using the
I'm trying to find something like Overall I like the idea behind #51 to pass along the children parameters and also in this case the request (maybe even extrapolate this to all available variables in that template - not sure the impact on Django' template variable resolution) |
Yeah, we are also using it together with HTMX, it's indeed cumbersome |
I opened a PR for this: #64 |
Any update about this feature? |
I'm considering passing the
request
object from the parent context to the component transparently if it's available. My reasoning is that a bunch of existing template tags require therequest
object to function.Thoughts?
The text was updated successfully, but these errors were encountered: