Fix ty type errors in header tests#3249
Merged
Merged
Conversation
Annotate new_headers dicts as dict[str, str] so the newer ty does not widen their value type to include None via .pop(..., None). Co-Authored-By: Claude Opus 4.8 (1M context) <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.
The
tybump in #3247 began flaggingEndpoint(headers=new_headers)in two tests, becausetywidens a dict's value type to includeNoneafter a.pop(..., None)call, making it no longer assignable toMapping[str, str]. This annotates the two affectednew_headersdicts asdict[str, str]so their declared type stays fixed.