-
Notifications
You must be signed in to change notification settings - Fork 51
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 pages to opt-in, instead of opt-out. #159
Conversation
@@ -301,6 +301,28 @@ You may, of course, chose the combination that best suits your needs. | |||
of trouble, please do not expect help from the maintainers of this | |||
plugin. | |||
|
|||
#### Solution 5: Make the rendering process opt-in, instead of opt-out | |||
|
|||
_From version x.x.x_ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what to show here, please feel free to fixup in your own commit!
If it were my design, I'd have this config renamed to something like |
Hah...
Yeah, exactly - disable macros globally, and then re-enable them for the pages that need to use macros.
If I was implementing it fom scratch, I would probably have picked upright logic too (rather than inverted)... but I didn't want to disrupt / confuse the |
This is attached to issue #162 (a slightly different solution was adopted). |
I really like that solution! 🙌 |
Thanks a lot for your helpful contribution. |
I have many, many pages, but would like to use Jinja2 rendering on only one new page.
This patch will make the
ignore_macros
configuration available at the global level, effectively permitting individual pages to "opt-in" usingignore_macros: true
, instead of only "opt-out" usingignore_macros: false
.