feat: suppress implicit safe integer bounds in markdown docs#18
Merged
feat: suppress implicit safe integer bounds in markdown docs#18
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
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.
Suppress implicit safe integer bounds in generated docs
Problem
Zod automatically assigns Number.MIN_SAFE_INTEGER and Number.MAX_SAFE_INTEGER as implicit bounds for integer fields when no explicit min or max is defined.
These default bounds were being rendered in the generated markdown documentation as “Min value” and “Max value”, even though they do not represent meaningful user-defined constraints. This added unnecessary noise to the output.
Solution
Filter out these implicit Zod defaults during documentation generation.