Hide default None value in cli_hide_none_type is set #720
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.
When a field defaults to None, displaying
(default: null)provides no additional information to users. The absence of a default value already implies None/null for optional fields, and this matches the behavior of most CLI tools (argparse, click) where optional arguments don't displaydefault: None. Users expect optional CLI arguments to default to None implicitly.This change aligns pydantic-settings with standard CLI tool conventions (argparse, click) where None defaults are hidden. Also, this reduces visual noise in help messages:
before
after
As this MR alters the behavior of
cli_hide_none_type, you might prefer adding another flag to support this, e.g.cli_hide_none_type_defaults?