feat(document): support schematype-level transform option #15163
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
1 task
hasezoey
approved these changes
Jan 8, 2025
hasezoey
reviewed
Jan 8, 2025
hasezoey
reviewed
Jan 8, 2025
Collaborator
hasezoey
left a comment
hasezoey
left a comment
There was a problem hiding this comment.
Eslint fixes (when fixing the unsupported syntax)
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.
Fix #15084
Summary
With a little bit of work, we can support
transformon a per-schematype basis, which can enable us to control how types end up being serialized to JSON. This is useful for custom schema types, as specified in #15084, also useful for controlling how buffers get serialized.Examples