Skip to content

docs: add class docstrings to concrete ParamType implementations#3296

Closed
mastash3ff wants to merge 1 commit intopallets:mainfrom
mastash3ff:docs/add-param-type-class-docstrings
Closed

docs: add class docstrings to concrete ParamType implementations#3296
mastash3ff wants to merge 1 commit intopallets:mainfrom
mastash3ff:docs/add-param-type-class-docstrings

Conversation

@mastash3ff
Copy link
Copy Markdown

Summary

The concrete ParamType subclasses that back the click.STRING, click.INT,
click.FLOAT, click.BOOL, and click.UUID constants are missing class-level
docstrings. All other ParamType subclasses with distinct behaviour
(Choice, IntRange, FloatRange, File, Path, Tuple) already have
class docstrings; this PR fills the gap for the five basic types.

Changes

  • StringParamType: describes the type, its constant, and bytes decoding behaviour
  • IntParamType: describes the type, its constant, and includes a usage example
  • FloatParamType: describes the type, its constant, and includes a usage example
  • BoolParamType: describes the truthy/falsy string values accepted and notes
    that Click uses this type automatically for is_flag=True options
  • UUIDParameterType: describes the type, its constant, and accepted string formats

StringParamType, IntParamType, FloatParamType, BoolParamType, and
UUIDParameterType are the backing implementations for the click.STRING,
INT, FLOAT, BOOL, and UUID constants respectively.  All other ParamType
subclasses with distinct behaviour (Choice, IntRange, FloatRange, File,
Path, Tuple) already have class docstrings; add the missing ones here.
@davidism davidism closed this Apr 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants