fix(templates): expose custom data tokens globally - #371
Draft
DavidBabinec wants to merge 1 commit into
Draft
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed
{data.<rowId>.<fieldId>}and resolve them in canvas previews, static publishes, holes, and infinite-loop fragmentsWhy
Custom data tables are the natural home for shared values such as a GitHub star count, but their rows were not available outside loop or post-type template scopes. Plain custom-data rows are also deliberately non-versioned, so the publisher must read their live cells rather than look for an active published row version.
User impact
Authors can insert a custom-data value into any compatible property and reuse it across ordinary pages. The canvas and published site resolve the same value; a later data change is included by the next Site publish.
Verification
bun test(6,621 pass)bun run buildbun run lintbunx tsc -b --pretty false