We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Suppose a rest directive can do things differently based on a config option (yes, abstract feature).
Currently, it would need to record a dependency on the conf.py file in order to react to config changes.
This feature would provide the directive developer a mechanism to declare a depedency on specific config key values.
The text was updated successfully, but these errors were encountered:
Doing #1854, aren’t you now?
Sounds like adding a ####MAGIC####CONFIG:REST_SUBSTITUTIONS dependency (like it’s done in post lists) and some simple handling would do it.
####MAGIC####CONFIG:REST_SUBSTITUTIONS
Sorry, something went wrong.
Actually,no, this was requested by @humitos for his fotorama stuff, but yes, that would also need it, and yes, that's the plan :-)
Implement depend-on-config-options for reSt extensions (Fix Issue #1919)
b565553
@humitos take a look, that implementation is not tested, see the doc diff for how it's supposed to work ;-)
Merge pull request #1927 from getnikola/do-1919
9442586
Done.
ralsina
No branches or pull requests
Suppose a rest directive can do things differently based on a config option (yes, abstract feature).
Currently, it would need to record a dependency on the conf.py file in order to react to config changes.
This feature would provide the directive developer a mechanism to declare a depedency on specific config key values.
The text was updated successfully, but these errors were encountered: