-
-
Notifications
You must be signed in to change notification settings - Fork 98
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
[BUG] ValueError in Dooit: SCREENS Contains Instance Instead of Callable Screen Type #198
Comments
Hi @zx0r , Yes The current version uses a very old release of Textual, the underlying TUI library hence the issue. How are you installing Plus, I'll make a new release tomm so things should sort out when the package is updated:) |
Hi again @zx0r ! Sorry totally forgot about this, I've released a newer version, are you familiar with gentoo packaging? |
Hey @zx0r , that was a question. I've got 0 idea about gentoo packaging. Is this the place where you got the package from? https://gpo.zugaina.org/app-text/dooit/RDep |
Hi bro) Project:GURU https://github.com/gentoo-mirror/guru/tree/master/app-text/dooit |
Hi @henri-gasc! Look like you made the contribution to GURU for dooit. Can you update to the latest version? I can help if required :) |
No need for help, I will update it soon. I did not see there was an update |
Thank you! Heads up: I'll also release a new version in a few hours with a patch bump. |
I pushed the update, you can close this issue |
@zx0r, please double check from your side and feel free to open any other issues if you have :) |
Did we solve your problem? Consider sponsoring my work through github sponsors 😄 |
Hi bro)
Describe the bug 🐛
Dooit Initialization Error: SCREENS Configuration Incorrectly Uses Instance
Additional context 📝
The error traceback indicated that the issue was caused by incorrectly instantiating the screens within the SCREENS dictionary. To fix this, the SCREENS declaration was modified to only include the class references without instantiation:
Screenshots 📺
The text was updated successfully, but these errors were encountered: