ndg: allow user-defined variables in Tera context#144
Merged
Conversation
Signed-off-by: NotAShelf <raf@notashelf.dev> Change-Id: I22bd9c5c4c272bb8779b04889751981c6a6a6964
Signed-off-by: NotAShelf <raf@notashelf.dev> Change-Id: Ia13433acf2832dbafe089ee5f090a09a6a6a6964
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #20
Adds support for user-defined template variables in the site configuration, allowing users to inject custom values into all Tera templates via the
[vars]table inndg.toml. Built-in variables continue to take precedence over user-defined ones.