We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I would be nice to have expanded type coverage.
Loosely, even if this isn't idiomatic splinter usage, I think the general benefits of annotations and typings still hold. I am fine to elaborate.
Specifically, I am running into any Any with BaseWebDriver's attribute .driver.
Any
BaseWebDriver
.driver
Where I have a function like:
def fill_helper(browser: BaseWebDriver, selectors_path: list[str], value: str) -> None: # ... pass
And mypy will raise:
mypy
.../test_website.py:31: error: Argument 1 to "fill_helper" becomes "Any" due to an unfollowed import [no-any-unimported]
Not relevant, but happen to be using:
The text was updated successfully, but these errors were encountered:
I'm a big +1 on this, but I don't think I'll have time to work on it on the short term. It is something we can make incremental progress though.
Sorry, something went wrong.
Once annotations are complete, I'd lie to request adding a PEP 561 py.typed marker as well.
py.typed
No branches or pull requests
Request
I would be nice to have expanded type coverage.
History
Example scenario
Loosely, even if this isn't idiomatic splinter usage, I think the general benefits of annotations and typings still hold. I am fine to elaborate.
Specifically, I am running into any
Any
withBaseWebDriver
's attribute.driver
.Where I have a function like:
And
mypy
will raise:Not relevant, but happen to be using:
The text was updated successfully, but these errors were encountered: