This is intended to be a two-way sync of Habitica and todoist. Any tasks that can't be found
in both services should appear on the others, with the same status. If you complete a task on one service,
it should appear as completed on another. Tasks that are created on Habitica should be sent to the 'Inbox'
project on Todoist.
AS A NOTE: in order to have two way syncing, you MUST have a paid copy of Todoist. It's not possible for me to port complete tasks from Todoist otherwise. If you do not have a paid copy of Todoist, the following will happen:
a) completed tasks will not sync between the services
b) tasks that you begin and complete from one service to the other will not transfer between the two.
That means that if you create a task in todoist and then check it off, right now it will _not_ send the points to Habitica.
I encourage people without paid todoist to pick up todoist-habitrpg, which doesn't care one way or the other. (I rather hope that kusold's success with that means that Habitica-todoist will be able to figure this out eventually, but right now that's my workaround.) Or you could pony up the $30 for a year's subscription of Todoist. I'm pretty sure it's worth it.
INSTALLATION
If you're lazy and comfortable with python, you can run:
pip
TASK DIFFICULTY
I originally felt that it would be good if task difficulty translated between tasks created on Todoist and
Habitica. Therefore, task difficulty should sync with the following code by default, as laid out in $PRIORITY_DOC:
Todoist priority Habitica difficulty
p1 Hard
p2 Medium
p3 Easy
p4 Trivial
If you'd like to change how the sync interprets difficulty or priority, please edit $PRIORITY_DOC. For example, my personal setup actually includes
translating Todoist p4 to Easy, rather than Trivial, because I find that Trivial yields so few rewards they aren't worth it to me.
USAGE
INSPIRATION
I'd like to credit several existing apps that I pulled from in order to create this. Notably:
-philadams' existing habitica app, for a lot of initial code and many helpful explanations of how to do things
also for existing API!
-Pytodoist
-Dee Dee whose scriptabit which provided a lot of ideas
THANKS
1 maintainer
Metadata
1 maintainer
Release files for habiticaTodo 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| habiticaTodo-1.2.0.tar.gz | 12.0 kB | Without provenance | Details for habiticaTodo-1.2.0.tar.gz |
Release files / habiticaTodo-1.2.0.tar.gz
| Download URL | habiticaTodo-1.2.0.tar.gz |
|---|---|
| Size | 12.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
24698756d79309cd75705b7da70e58042481e8ef0521bab16fea93fdeb839dd8
|
|
BLAKE2b-256 checksum How to use checksums |
e85390e85471a5fd02cfecf9f4b2d62f576d0beb404d0777f7c2c6a85fa63fcc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for habiticaTodo 1.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
