Type fixes #249
Merged
Type fixes #249
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
gadomski
approved these changes
Jun 24, 2022
|
@matthewhanson @gadomski Any chance we could merge this? I'm working on a PR for #241 and it would be nice to start with this in |
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.
Related Issue(s):
None
Description:
mypytype checking to the lint script and the pre-commit configmypyagainst all Python files in repo (this helped catch some issues like the implicit re-exports that were not caught by running it just against the source code)Client._stac_io__init__.py(this also helps with autocomplete in some development tools like VSCode).PR Checklist: