-
Notifications
You must be signed in to change notification settings - Fork 14
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Refactoring typing
imports / usage
#958
Comments
I think that's a good idea. Let's do it this way, it's much cleaner. |
We should also decide for one task decorator syntax. Currently we have this (where we import the entire viur-core/src/viur/core/securitykey.py Line 114 in 09312ee
and this (where we import every member of the module): viur-core/src/viur/core/skeleton.py Line 1317 in 09312ee
|
We should use |
Mostly replaced `typing` by `t` Resolve the typing part of #958 --------- Co-authored-by: Jan Max Meyer <jmm@phorward.de> Co-authored-by: Sven Eberth <mail@sveneberth.de>
Mostly replaced `typing` by `t` Resolve the typing part of #958 --------- Co-authored-by: Jan Max Meyer <jmm@phorward.de> Co-authored-by: Sven Eberth <mail@sveneberth.de>
fixed by #986 |
We have a lot of
typing
imports likefrom typing import this, that, ...
Sometimes they are really long:
viur-core/src/viur/core/skeleton.py
Line 12 in 8809c50
I saw in other projects they import
typing
aliased witht
(ìmport typing as t
) and writeargument: t.Any
.Maybe we should do this in the viur-core too. What do you think, should this be part of our coding conventions?
The text was updated successfully, but these errors were encountered: