-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
built-in dependency management across macros #31
Comments
Here's an example from a codebase that's actually in use: http://paste.pocoo.org/show/489070/ Fortunately I had the luxury of being able to move the dump() calls to the end of my base template because otherwise the register() calls were happening after (so dump() would output nothing). But having to worry about the order of these calls is a flaw of this solution. Perhaps a built-in facility for this could guarantee the dump calls being evaluated last. |
we're interested in something very similar, has any more thought been given toward how this could happen? the end result I'd look for is a base template that looks like:
and dateselector.tpl is:
a few questions as I'm getting started looking at how to do this in more depth:
this proposal on stack exchange achieves this in a way: but I'm not sure about the use of I guess what I'm saying is, we'd love to put in some work on writing such an extension, and a nudge in the right direction would be helpful. thanks. |
Closing as I'm not exactly sure what's being asked for anymore, and the complexity does not seem like a good fit in Jinja right now. |
Some macros may depend on other macros. Currently if you'd like to manage dependencies across macros, you have to roll your own (a la http://paste.pocoo.org/show/379402/ ).
The text was updated successfully, but these errors were encountered: