Closed sir-sigurd closed 2 months ago
Attention: Patch coverage is 88.25911%
with 87 lines
in your changes missing coverage. Please review.
Project coverage is 37.46%. Comparing base (
64e081c
) to head (e38e644
). Report is 4 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This looks great! I assume in the final version it will be something like "quilt3.admin"; 'adminql' is too much information
My main concern is that I find the name and type of "role" confusing; when do I use a role_id vs a role_name?
Is it possible to:
@nl0 do you think anything needs to be done other than tests?
@nl0 do you think anything needs to be done other than tests?
idk, seems good enough. maybe add some more management commands? e.g. make and admin, edit an email, etc?
CI currently fail because of https://github.com/jd/tenacity/issues/471
@nl0 does it make sense to rename some functions set_role -> set_user_role add_roles -> add_user_roles remove_roles -> remove_user_roles ?
or maybe use prefixes for consistency? i.e.
get_user -> user_get get_users -> user_list set_role -> user_set_role ?
does it make sense to rename some functions?
yeah i think so
or maybe use prefixes for consistency? i.e.
that feels like a good intent, but the resulting names don't look too nice, so... your call.
imo it would look nice if we had some sort of a namespace (e.g. admin.users.list
or smth, idk)
imo it would look nice if we had some sort of a namespace (e.g.
admin.users.list
or smth, idk)
I made this change
Description
TODO
ImportError: cannot import name 'Annotated' from 'typing'
(drop Python 3.8?)build.py
for new docstrings