Skip to content

Inesa/v1 docstrings cupertino #5291

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 35 commits into
base: v1
Choose a base branch
from
Open

Conversation

InesaFitsner
Copy link
Contributor

@InesaFitsner InesaFitsner commented May 8, 2025

Description

Test Code

# Test code for the review of this PR

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist

  • I signed the CLA.
  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
  • New and existing tests pass locally with my changes
  • I have made corresponding changes to the documentation (if applicable)

Screenshots

Additional details

Summary by Sourcery

Add comprehensive docstrings to Cupertino controls in the Flet Python SDK, improving documentation and type hints for various iOS-style UI components

Enhancements:

  • Improved type hints and documentation for Cupertino controls
  • Added more descriptive property explanations
  • Standardized docstring format across Cupertino controls

Documentation:

  • Added detailed docstrings to multiple Cupertino control classes, explaining properties, types, and usage

@InesaFitsner InesaFitsner requested a review from FeodorFitsner May 8, 2025 20:06
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.

1 participant