ForumsSearch
Search results for "Posted by JTMcFarland"
| Author | Message |
|---|---|
|
JTMcFarland |
Posted Dec 22, 2017 in: Issue with rows\get.php returning ref field
Score: 1
Endpoint https://api.toodledo.com/3/rows/get.php appears to be supplying a ref value. I'm not sure why it's there or where it came from.
Based on the documentation at http://api.toodledo.com/3/rows/index.php I expect ref could be returned by add, edit and delete, but not get or deleted. I would appreciate any feedback on this issue. |
|
JTMcFarland |
Posted Nov 27, 2017 in: Problem with results from deleted.php
Score: 1
I tested, and I get the same result with an integer.
|
|
JTMcFarland |
Posted Nov 26, 2017 in: Problem with results from deleted.php
Score: 1
I've run across something I'm not sure I understand. It seems that I'm getting null back for some deleted requests and data indicating there are 0 records to return for others. I was expecting that both calls below would return the same content indicating there are no records which match the specified criteria. Please help me understand what's happening here.
'https://api.toodledo.com/3/tasks/deleted.php?after=1511674071.0' status_code = 200 content = b'[{"num":0}]' 'https://api.toodledo.com/3/lists/deleted.php?after=1511674071.0' status_code = 200 content = b'null' These results have been consistent and repeatable for me. |
|
JTMcFarland |
Thanks for the feedback on this. :-)
|
|
JTMcFarland |
I'm not sure I understand this functionality correctly. When I delete a task, lastedit_task gets updated indicating there was a change made, yet calls to the API for edits yield no result. This seems to mean the request for edits was unnecessary. This seems important based on the API documentation <http://api.toodledo.com/3/account/doc_sync.php> where it states "It is very important to be frugal with the API". So how can I avoid making the unnecessary request for edits when only deletes have occurred?
According to the API documentation for /3/account/get.php is as follows... lastedit_task : A timestamp that indicates the last time that any task was added or edited on this account. You can quickly check this field to determine if you need to download updates. lastdelete_task : A timestamp that indicates the last time that any task was deleted from this account. You can quickly check this field to determine if you need to identify and remove tasks from your application. Based on the recommendations flowchart for task syncing (at http://api.toodledo.com/3/tasks/index.php), I see the association between lastedit_task and "tasks/get.php" as well as lastdelete_task and "/tasks/deleted.php". However I see no indication that lastedit_task should yield any kind of result when a task is deleted. If this is correct, I'm not sure I understand the value in updating lastedit_task when a task is deleted. It seems to be causing unnecessary API calls from a client, and unnecessary load on the service/servers when checking for non-existing edits. Is there a use case I'm missing here, or something I'm misunderstanding? |
|
JTMcFarland |
I recently noticed that when I delete a task, the server seems to be updating both lastEditTask as well as lastDeleteTask. My understanding is that it should be updating only lastDeleteTask in this scenario. I'm using the toodledo website to delete the task, and then pulling both fields from /3/account/get.php
|