如何获取 jinja 2 模板中所有变量的列表
我正在尝试获取模板中所有变量和块的列表。我不想创建自己的解析器来查找变量。我尝试使用以下代码片段。
from jinja2 import Environment, PackageLoader
env = Environment(loader=PackageLoader('gummi', 'templates'))
template = env.get_template('chat.html')
template.blocks
是字典,其中键是块,如何获取块内的所有变量?
I am trying to get list of all variables and blocks in a template. I don't want to create my own parser to find variables. I tried using following snippet.
from jinja2 import Environment, PackageLoader
env = Environment(loader=PackageLoader('gummi', 'templates'))
template = env.get_template('chat.html')
template.blocks
is dict where keys are blocks, how can I get all variables inside the blocks ?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(9)
由于没有人回答这个问题并且我找到了答案,
这将产生未声明变量的列表,因为这不是在运行时执行的,所以它将产生所有变量的列表。
注意:这将生成使用
include
和extends
包含的 html 文件。Since no one has answered the question and I found the answer
This will yield list of undeclared variables since this is not executed at run time, it will yield list of all variables.
Note: This will yield html files which are included using
include
andextends
.我有同样的需求,并且编写了一个名为 jinja2schema 的工具。它提供了一种启发式算法,用于从 Jinja2 模板推断类型,也可用于获取所有模板变量(包括嵌套变量)的列表。
这是这样做的一个简短示例:
I had the same need and I've written a tool called jinja2schema. It provides a heuristic algorithm for inferring types from Jinja2 templates and can also be used for getting a list of all template variables, including nested ones.
Here is a short example of doing that:
对于我的鹈鹕主题,我创建了一个工具来分析模板文件中的所有 jinja 变量。
我分享我的代码
该脚本从模板文件中存在的所有变量生成示例配置,并从我的官方 pelicanconf.py 获取变量
从模板文件中提取所有变量的函数
完整的脚本
该程序的示例结果
有关此脚本的更多详细信息,请参阅 https://github.com /badele/pelican-theme-jesuislibre
For my pelican theme, i have created a tools for analyse all jinja variables in my templates files.
I share my code
This script generate a sample configuration from all variables exists in template files and get a variables from my official pelicanconf.py
The function that extract all variables from template file
The complete script
The sample result of this program
For more détail of this script see https://github.com/badele/pelican-theme-jesuislibre
对于那些想要找出所有变量而不仅仅是需要从外部设置的变量的人来说。可以执行以下操作:
输出是:
有人正在询问字段,它也可以轻松存档:
for ones want to find out all variable not just the variable need to be set from outside. one can do following:
output is:
Someone is asking for the fields, it can also easily archived:
对我来说 jinja2.meta.find_undeclared_variables(parsed_content) 不太合适,因为它不提供嵌套变量。
jinja2schema
工具对于简单的场景来说还不错,但是对于所有循环和其他 jinja2 黑暗力量,它会失败并出现错误。我尝试过 jinja2 数据结构,并且能够获取所有变量,包括嵌套变量。对于我的用例来说,这已经足够了。也许这对其他人也有帮助:)
这是代码:
For me
jinja2.meta.find_undeclared_variables(parsed_content)
is not a good fit because it does not provide nested variables.jinja2schema
tool was kinda ok for simple scenarios but with all the loops and other jinja2 dark powers it was failing with errors.I have played around with jinja2 data structures and was able to get all variables including nested ones. For my use case this was enough. Maybe this will also help for somebody else :)
Here is the code:
为什么不使用正则表达式?
如果发现使用正则表达式更容易:
Why not regex?
If find it a lot easier to use
regex
:基于 @Kracekumar 的答案,但对于最简单的用例,即从作为字符串参数传递的模板中提取令牌,没有加载语义或过滤器覆盖:
tokens
将是一个集合。Based on @Kracekumar's answer, but for the simplest use-case of just extracting tokens from a template passed as a string argument with no loading semantics or filter overrides:
tokens
will be a set.尽管最上面的答案附有支持
extends
的注释,但实际上并非如此。env.loader.get_source
只能解析当前模板。这是 Violet Shreve 在最佳答案中的评论提供的建议的实现。
Though the top answer attaches a note supporting
extends
, actually, it's not. Theenv.loader.get_source
can only parse the current template.Here's an implementation for the advice provided by the Violet Shreve's comment in the top answer.
下面是可用于获取变量属性的示例代码
就像
{{ Something.nested }}
一样,不使用任何第三方库。代码
输入
输出
注意:
可以修改此代码以执行递归操作以获取更深层次的嵌套值,例如
{{ some.more.some_more.once_more }}
Below is the sample code that can be used get properties of the vars
like
{{ something.nested }}
, without using any third party library.Code
Input
Output
Note:
This code can be modified to perform a recursive operation to fetch deeper nested values like
{{ something.more.some_more.once_more }}