🏷️ Fix type annotations on public API#562
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Summary
The package ships
py.typed, so these incorrect annotations are user-facing:names.py:name_fields: Tuple[str](a 1-tuple type) →Tuple[str, ...]in both middleware constructors and thename_fieldsproperty.latex_encoding.py:keep_math,enclose_urls,keep_braced_groups,keep_math_modedeclaredbool = None→Optional[bool] = None.entrypoint.py:parse_stringnow annotated-> Library; lowercasetuple[...]aligned to thetyping.Tuplestyle used everywhere else.No runtime behavior change. Adding mypy/pyright to CI (which would have caught #529) is left as a possible follow-up.
Fixes #538
🤖 Generated with Claude Code