You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be helpful if there was a way to call app.warn() / builder.warn() from jinja template (maybe .debug() and .info() as well). This would be particularly helpful for theme development... I've got a .css_t file which does some parsing / numeric calculations, and would like to be able to display a cmdline warning to the user that some of the theme.conf inputs couldn't be parsed / were invalid.
Something further, like an ability to abort compilation with an error message, would be icing, but looking at jinja2glue.py's environment setup, it looked like inserting builder.warn() into the jinja environment wouldn't be hard, presuming there weren't security / design considerations I'm not aware of.
The text was updated successfully, but these errors were encountered:
tk0miya
added a commit
to tk0miya/sphinx
that referenced
this issue
Mar 18, 2018
It'd be helpful if there was a way to call app.warn() / builder.warn() from jinja template (maybe .debug() and .info() as well). This would be particularly helpful for theme development... I've got a .css_t file which does some parsing / numeric calculations, and would like to be able to display a cmdline warning to the user that some of the theme.conf inputs couldn't be parsed / were invalid.
E.g:
Something further, like an ability to abort compilation with an error message, would be icing, but looking at jinja2glue.py's environment setup, it looked like inserting builder.warn() into the jinja environment wouldn't be hard, presuming there weren't security / design considerations I'm not aware of.
The text was updated successfully, but these errors were encountered: