fix: typing for file opened for writing with click #403
Conversation
This file contains 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
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #403 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 23 23
Lines 2078 2078
Branches 334 334
=========================================
Hits 2078 2078
☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
clickopens files for writing lazily, meaning that a file opened for writing is not immediately anio.TextIOWrapperbut aclick.utils.LazyFilefor the purpose of typing: https://click.palletsprojects.com/en/8.1.x/api/#click.File. This was flagged bytypeguardversion4.0.0rc4(which will be adopted after full release via #391).