Replies: 1 comment 1 reply
-
Ok, I believe the hard-coded inclusion of the user_config in the main cli to be the culprit here. I have, for the time being, simply opted to create my own copy of the main.py cli with the user config removed. I have only tested it so far with the migrations subcommand, but that works, so going for the moment with the assumption that things will work in general. One weird caveat: It seems that I cannot have my custom User in a package called user. I can name the app user, and that is ok, but if it is in my code under |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am wondering if this is expected behavior. The following items show even though I have not registered
piccolo.apps.user.piccolo_app
in my AppRegistry:Ideally, it seems like these commands would only be available if I am using the user app. Perhaps there is a way to explicitly disable them?
Beta Was this translation helpful? Give feedback.
All reactions