-
Notifications
You must be signed in to change notification settings - Fork 198
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
Allow at least one kind of substitution inside directive #680
Comments
Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗 |
Related to #637. |
While this doesn't fix the fact that .. replace:: does not work within eval-rst, it does make it possible to perform substitutions within eval-rst using the same substitutions available to Jinja substitutions. Related: executablebooks#680 Signed-off-by: Chance Zibolski <[email protected]>
While this doesn't fix the fact that .. replace:: does not work within eval-rst, it does make it possible to perform substitutions within eval-rst using the same substitutions available to Jinja substitutions. Related: executablebooks#680 Signed-off-by: Chance Zibolski <[email protected]>
While this doesn't fix the fact that .. replace:: does not work within eval-rst, it does make it possible to perform substitutions within eval-rst using the same substitutions available to Jinja substitutions. Related: executablebooks#680 Signed-off-by: Chance Zibolski <[email protected]>
Context
This issue is closely related to #172, especially #172 (comment).
As @nickcrider was explaining, there is an edge case where users needs to use
{eval-rst}
but are unable to use any kind of substitution as Jinja's{{ }}
won't be evaluated and reST substitution.. |any| replace::
does not work either (throwingUndefined substitution referenced: "any"
error).To be a bit more precise, in my case, I'm using
{eval-rst}
to handle more complex tables offered by reST (to merge cells essentially). And it's quite a known fact that tables are hard to maintain when the content gets a bit large.Until now, with basic markdown tables I was able to use Jinja substitution :
But with reST tables, I cannot manage to make it work :
Proposal
I understand that this is not that simple, but that would be really great to have some kind of support for reST substitution inside
{eval-rst}
blocks.Or any other way of doing text substitution.
I am aware that sphinx-substitution-extention supports
rst_prolog
but I cannot set these text variables inside theconf.py
file. Each text is very page related and that would be very confusing to move it in the config file.Maybe I'm missing something here ?
Thank you very much 🙏
Tasks and updates
No response
The text was updated successfully, but these errors were encountered: