-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add mypy checks #5
Conversation
Second option is more obvious for sure. However:
I would suggest either leave the first one or use second with some dependency caching. |
* add ydb_connector * lint * ydb docker * add setup extra * feature/ydb_connector: fix merge * feature/ydb_connector: massive upd, wip * feature/ydb_connector: fix sql, mongo, redis * fix: adapt ydb contexts serialization for uuid (#5) * fix: change context id to str type * fix: change id type to utf8 * fix: change serialization method for uuid Co-authored-by: Denis Kuznetsov <kuznetsov.den.p@gmail.com> * feature/ydb_connector: fix ydb * feature/ydb_connector: fix style * feature/ydb_connector: rm useless files & upd examples Co-authored-by: Denis Kuznetsov <kuznetsov.den.p@gmail.com> Co-authored-by: Evgeniy Egorov <90514210+EvgeniyEgoorov@users.noreply.github.com>
Second option is faster then our current unit-tests (because of that we do not have to wait three linting tests) and it's more atomic style. So I prefer the second one. |
We will wait until the end of addon's mega-merges. |
Do we need this PR, i think it can be closed |
I think it should be used to add mypy check. The name of the branch is |
As mentioned here viewing codestyle check results is not convenient.
This pull request solves that problem in two ways:
In my opinion, the second solution is better.