-
-
Notifications
You must be signed in to change notification settings - Fork 405
typing: add type hints to parser helper functions (#938) - #1743
typing: add type hints to parser helper functions (#938) #1743DaBestCode wants to merge 1 commit into
Conversation
This pull request did not pass quality checks and AI use is suspected. Please review Contribute and make any necessary amendments.
Profile summary:
GitHub user: DaBestCode
🟢 No concerns found with user's profile.
🟢 No concerns found with recent PR activity.
🟢 No concerns found with recent issue activity.
For a more detailed report, run `gh-profiler DaBestCode`.
Full profile
GitHub user: DaBestCode
🟢 No concerns found with user's profile.
🟢 Account age: 2 years
🟢 Profile information:
name: Pruthvi Nandan Janga
blog: https://myportfolio-phi-ebon.vercel.app/
email: pjanga@asu.edu
bio: LeetCode Freak
linkedin: https://www.linkedin.com/in/pruthvi-janga-9609a3238
Empty fields: company, location
🟢 No concerns found with recent PR activity.
1 PR opened in the last 21 days.
0 opened against repos the user owns.
0 opened against repos in publicly associated orgs.
1 opened against external repos.
🟢 0 of 1 external PRs merged in the last 21 days.
🟢 0 of 1 external PRs closed without merging in the last 21 days.
🟢 No concerns found with recent issue activity.
🟢 No new issues opened in the last 21 days.
stevepiercy
commented
Aug 31, 2026
CI fails == no review
@DaBestCode please follow our contributing guidelines. Thank you!
@niccokunzmann
niccokunzmann
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! The change looks technically valid!
Could you give more detail about the AI use, please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, please mention the model that you used.
niccokunzmann
commented
Sep 2, 2026
@stevepiercy over to you: Have a look at the small docs change or just merge it when the changelog entry is ok for you.
niccokunzmann
commented
Sep 2, 2026
@DaBestCode Welcome to icalendar! Nice to review your PR :)
Could you please format the code? We use a code formatter so that it always looks reliably the same. Please see here. https://github.com/collective/icalendar/actions/runs/33359907834/job/99389117324?pr=1743
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't include the issue number, as it's included in the filename. Also give yourself credit.
Linked issue
Description
This pull request adds comprehensive type hints to parser helper functions in the icalendar library, contributing to issue #938's goal of adding type hints throughout the codebase.
Changes Made
src/icalendar/parser_tools.py:to_unicode()docstring with a "Returns" section to better document the function's return behaviorsrc/icalendar/parser/parameter.py:-> Callableto thesingle_string_parameter()decorator functionupper: bool = Falseto clarify theupperparameter's typedecorator():-> propertyfget():-> str | None(getter returns optional string)fset():-> None(setter returns None)fdel():-> None(deleter returns None)news/938.chore.2:Benefits
Checklist
Additional information
pytest src/icalendar/tests/test_unit_parser_tools.pyand parameter-related tests)|)