fix: write textTransform to schema-valid asset field - #184
Merged
Merged
Conversation
added 2 commits
September 15, 2026 03:04
Text transform wrote `asset.style`, which Zod rejects on TextAsset (unrecognized_keys). textTransform belongs on asset.style only for rich-text / rich-caption; skip the update for other asset types.
|
🎉 This PR is included in version 2.19.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Why
Text transform wrote
asset.style, which Zod rejects on non-rich assets (unrecognized_keys: style).textTransformis valid only on rich-text / rich-captionasset.style.Verify
npx jest tests/rich-text-transform.test.tsRisk
Low. Style writes are gated to schema-supported asset types; plain text transform becomes a no-op rather than throwing.