feat: add presetContent for template builder#2856
Open
artem-harbour wants to merge 1 commit intomainfrom
Open
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
78f05dd to
43d8fb3
Compare
43d8fb3 to
40cd1bb
Compare
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.
Linear: SD-2548
Added presetContent support to Template Builder field definitions for block fields, wiring it into the existing insertStructuredContentBlock flow (no new insertion path).
Block fields now insert preset HTML/JSON when provided, while block fields without presets keep the existing text fallback; inline fields continue to ignore presetContent.
Included insertion-flow tests, updated package/solution docs, and added demo examples (Sample Table with visible borders and Sample List).