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
First of all, thanks for this 馃槵 API looks very promising!
One thing which would be nice to have, an endpoint which returns the timestamp of last modify action.
The problem it solves
I'm trying to write a cli app, which turned out to be extra slow, since I didn't cache yet (and you know how "easy" cache invalidation is 馃槵). Since I'll try to use todoist from multiple sources, I have no idea if there is a new change which is introduced by the other app (e.g. phone) before each run. Having a simple timestamp, accessible via cheap api call (way cheaper from pulling everything) would make cache invalidation easier.
Alternatives
I am currently pulling all tasks (or a whole project) depending on the requirement, before each action. I can maybe add it, but there is no way to know when to update, as long as other client can add/remove stuff. An optimistic timeout for the local cache might be helpful too.
The text was updated successfully, but these errors were encountered:
Enhancement description
Hi there 馃憢
First of all, thanks for this 馃槵 API looks very promising!
One thing which would be nice to have, an endpoint which returns the timestamp of last modify action.
The problem it solves
I'm trying to write a cli app, which turned out to be extra slow, since I didn't cache yet (and you know how "easy" cache invalidation is 馃槵). Since I'll try to use todoist from multiple sources, I have no idea if there is a new change which is introduced by the other app (e.g. phone) before each run. Having a simple timestamp, accessible via cheap api call (way cheaper from pulling everything) would make cache invalidation easier.
Alternatives
I am currently pulling all tasks (or a whole project) depending on the requirement, before each action. I can maybe add it, but there is no way to know when to update, as long as other client can add/remove stuff. An optimistic timeout for the local cache might be helpful too.
The text was updated successfully, but these errors were encountered: