-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Clarify docstrings for updated DbApiHook #27966
New issue
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
Conversation
| returned to XCom and generally fit in memory. As an optimization, handler is usually not executed | ||
| by the SQLExecuteQuery operator if `do_xcom_push` is not specified. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this bit about sql execute operator, i thought isn't really relevant to hook.run docstring.
|
Line too long :( |
|
Installed pre-commits really save on iterating with CI @dstandish 😛 |
yeah, sigh... i have them enabled but i have flake8 and mypy disabled because.... iteration time 😎 just too slow on mac... although.... it was a while ago i last checked |
Let's speed'em up. On my M1 I have completely no problems with slow iteration time on commits :) |
|
BTW. |
yes this is how i have it configured |
|
Haha I am familiar to this as well 😂. What I do now is configure mypy and flake as linter in my IDE. This way it is really easy to see/resolve and iterate on typing error. Then the pre-commit hook are just an extra check :) |
Started off by fixing typo, replacing
last_statementwithreturn_lastbut then tried to clarify the language a bit here and there.