-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Improved module detection, configuration, and added support for non-standard modules #56
Improved module detection, configuration, and added support for non-standard modules #56
Conversation
Yeah I'll try to get those done. |
I added the #48 changes and will look at the #27 changes next. Will also need to do some testing. #27 has some generic improvements which I'll at least integrate, but having to install all modules into path would be something I wouldn't prefer. I think it'd be better to have a global config file with a list which just happens to include all the aw's own modules by default. This'd make it much easier to add external modules without changing the source code and would also theoretically support having a "/modules" directory somewhere which could be sourced by the user. @ErikBjare Whats your opinion about automatic path detection vs a "possible modules" list and trying to find those modules? It's been quite a few years since #27 |
This pull request introduces 1 alert when merging 1dc943e into 8b03043 - view on LGTM.com new alerts:
|
About the config introduced in #27, I'd like to see the config file use An option is to simply rewrite |
I'd like @johan-bjareholt's comments on that as well. |
So I guess there are two questions:
It doesn't make much sense to me to be able to configure possible modules (as we will be able to figure out which are available anyway from the PATH and subdirectories) but there needs to be a way to specify which modules to run on startup (apart from the CLI flag). |
…ivityWatch#47 NOTE: `ConfigParser` does not correctly store array values. Store module lists as json.
1dc943e
to
94dc1df
Compare
This pull request introduces 1 alert when merging 94dc1df into 481ace6 - view on LGTM.com new alerts:
|
…eating module menu
…improved-module-detection
@ErikBjare I have now merged #27 and #48, so they can be closed. I also generally improved typing support everywhere around aw-qt. (TODOs moved to top comment) |
This pull request fixes 1 alert when merging ea9d196 into 481ace6 - view on LGTM.com fixed alerts:
|
This pull request fixes 1 alert when merging bfd13d7 into 481ace6 - view on LGTM.com fixed alerts:
|
bfd13d7
to
a7c098c
Compare
Update poetry lockfile to include stubs
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@xylix I started working on TOML support in aw-core here: ActivityWatch/aw-core#88 |
variable and manually splitting
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's about time we try to merge this. I'll move all the TODOs to the top comment.
This comment has been minimized.
This comment has been minimized.
I merged master into the branch and fixed a few things. Should be ready to merge now. |
This comment has been minimized.
This comment has been minimized.
This pull request introduces 6 alerts and fixes 1 when merging 01378f1 into 20261da - view on LGTM.com new alerts:
fixed alerts:
|
This pull request fixes 1 alert when merging 157a546 into 20261da - view on LGTM.com fixed alerts:
|
I'm just going to YOLO this and assume it will work fine on Windows (my only concern is the use of Merging as soon as CI passes. |
Great, nice that you got this finished! |
I will test it for Windows. If I find a error, I will report it here. |
Will improve module detection, and aims to add config file support for _available_modules and autostart lists
Merges and closes #27 and closes #48
TODOs:
Write config as commented out toml instead of old formatWe're skipping this.