-
Notifications
You must be signed in to change notification settings - Fork 14
Daily or to-do automatically turned into a habit and deleted name #34
Comments
Yesterday while I was looking closer at the documentation I noticed that the way we are checking off ToDos is not actually the way are supposed to. We are using an API that is meant for signaling the direction for Habits. It's in my tasklist, but I'm not sure if I will be able to get with it tonight. BTW, thank you @cygnoir! You are our best bug finder. 👍 |
@kusold You're welcome! I love helping to fix things and I sure do love HabitRPG. Also I'm glad to hear that I'm not just a big ol' pain the butt. ;) |
@cygnoir @kusold This habit was probably caused by todoist-habitrpg, but not necessarily so. Every time a score function is sent to habit, it looks for task with the id submitted. If it does not exist, it creates a new habit using that id for the name and id. So if a task got deleted in HRPG, and todoist-habitrpg had a history for it and tried to resync it, it would become a habit (since it would send the old, deleted id). However, some times that just randomly happens do to a sync error on the server. People who don't use any 3rd party addons get them from time to time. Regardless, it should be safe to delete it. If it reappears after the next sync, that'd be something to note. At that point, I'd probably make a copy of your |
My theory on what happens:
There is a step missing between 3 & 4 that I'm unsure about, but that's my theory. It looks like I won't be able to just simply rip out the |
Checking back in: I deleted it and it did not reappear. If another one appears, I will note it here. |
Hi, all. I'm sorry to open another issue, but here I am.
I created either a daily or to-do today that was somehow turned into a habit. I have been revamping my tasks in Todoist today so I'm not sure which one it is, and its name was deleted. Here is its info:
I'm not using any "third-party service" aside from this one so I'm not sure what happened here.
The text was updated successfully, but these errors were encountered: