Skip to content

fix: example fields substitution in content filename key#14

Open
olizilla wants to merge 1 commit intopages-cms:mainfrom
olizilla:patch-1
Open

fix: example fields substitution in content filename key#14
olizilla wants to merge 1 commit intopages-cms:mainfrom
olizilla:patch-1

Conversation

@olizilla
Copy link

The keys in double parentheses do not appear in the rendered docs site.

Screenshot 2025-07-16 at 13 09 45

this change also removes a duplicate key definition from the Settings section.

The keys in double parentheses do not appear in the rendered docs site.

Also removes a duplicate key definition from the Settings section
@Nathanjms
Copy link

Nathanjms commented Jan 17, 2026

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants