-
Notifications
You must be signed in to change notification settings - Fork 0
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
Paring down the features to what is most useful #4
Comments
The new API is done by me so if anything doesn't make the blame is with me. |
Are you using the package yourself? How do you use it? That's more of what I'm getting at. Storing the task ids whenever they are created... that could work. It would not help me with doing what I had originally hoped-- a basic example being, create a plot with the count of tasks completed every week since I started using Todoist in 2014. But it might allow that going forward. It seems like Todoist has created the API with other applications that a user might have for modifying Todoist data, but not for "reporting" or analysis. |
Emi: I tried to transfer this repo to you but couldn't do it since you have one of the same name. Once you delete it, I'll move it over to you. I stopped using todoist many years ago so this api is not of much interest to me these days. |
@karthik I don't have a repo of the same name funny @chrisumphlett I'll have to dig a little deeper to see if that can be done |
I don't know what the original intent of karthik was but I think to make the package more effective you should remove some functions for which I do not see much of a use case (and then consequently less time will need to be devoted to those going forward, and more development can happen on useful functions).
For removal, I am specifically referring to the task_reopen. That requires the id (at least that was my impression looking at the todoist API documentation), and you can't find the id because task_get_all will only give you active tasks.
I believe that this might also apply to the other ..._id functions. I wouldn't know the id for task_get_by_id unless I first did task_get_all; and if I've done that, I already have the info for that task.
In terms of which functions are most useful I was hoping to be able to get completed activity. The sync API has some ability to query the activity log; I was hoping that there would have been something that would allow a function like: task_get_all_completed. Have I missed something? Is it possible?
The text was updated successfully, but these errors were encountered: