You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 20, 2021. It is now read-only.
If I want to programatically trigger any action on the creation of a new task, regardless of which list it was created on, currently the only way around I can think of (not even sure if possible) would be to:
GET a.wunderlist.com/api/v1/root and check revision until it changes
Fetch all lists available with GET a.wunderlist.com/api/v1/lists
Loop through each list with GET a.wunderlist.com/api/v1/tasks and progressively build up a global tasks list.
I understand that Tasks are childs of Lists, so maybe, okay, it might not be trivial to implement this by making parameter list_id in GET a.wunderlist.com/api/v1/tasks optional, making it accept -1, etc.
But I mean... it looks – for me – as simple as it gets: "fetch all tasks for a user".
If the problem is really related to the parent<>child issue this, could maybe be a method of the user object or something like that... 🤷♂️
Is there any particular reason this is not a feature already?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If I want to programatically trigger any action on the creation of a new task, regardless of which list it was created on, currently the only way around I can think of (not even sure if possible) would be to:
GET a.wunderlist.com/api/v1/root
and checkrevision
until it changesGET a.wunderlist.com/api/v1/lists
GET a.wunderlist.com/api/v1/tasks
and progressively build up a global tasks list.But I mean... it looks – for me – as simple as it gets: "fetch all tasks for a user".
If the problem is really related to the parent<>child issue this, could maybe be a method of the user object or something like that... 🤷♂️
Is there any particular reason this is not a feature already?
The text was updated successfully, but these errors were encountered: