jinja2.meta.find_undeclared_variables equivalent

[morenol]

http://code.nabla.net/doc/jinja2/api/jinja2/meta/jinja2.meta.find_undeclared_variables.html

I see that it was implemented but removed in #105

With the custom delimiters feature in place, maybe you could consider PRs adding that feature again?

[mitsuhiko]

Very possible to bring it back. I think the bigger question is what you want to use it for so I better understand the motivation.

[morenol]

My use case is something like:

given:

   - uses: actions/checkout@v3
      with:
        github-token: ${{ secrets.GITHUB_TOKEN }}

Get all the things that I need to have in context so it can render successfully. So, in this case secrets.GITHUB_TOKEN.

I see that the python library does not have a way to do it (nested undefined variables). Maybe I need to create something like jsonschema on top of minijinja.

In any case, thanks for bringing back that api again

[mitsuhiko]

For what it’s worth it doesn’t do anything for nested constant attribute access.

[mitsuhiko]

I'm still not sure about the usefulness of this in the current form. Potentially the nested attribute information would make this at least somewhat more useful. Before releasing I want to reconsider this.