fix: example fields substitution in content filename key
#14
Conversation
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
The keys in double parentheses do not appear in the rendered docs site. Also removes a duplicate key definition from the Settings section
|
Thanks for this! Was trying to get this to work and realised the same - the double quotes aren't even needed anyway, so this PR looks good to me. I've ended up with filename: "{year}-{month}-{day}-{primary}-{fields.start_date}.json"Shame it's not been merged in yet, is the repo active? |
Nathanjms
approved these changes
Jan 17, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The keys in double parentheses do not appear in the rendered docs site.
this change also removes a duplicate key definition from the Settings section.