That's what I was referring to by todos.xml. From the API docs, /todos.xml, /contexts/ID/todos.xml, /projects/ID/todos.xml, all I get returned are the active todos, I assumed that was the intention but maybe I'm missing something? I know I can access an individual completed todo using /todos/id.xml, but don't see how to 'discover' such a todo through the API.
...found my problem with inserting pre-completed todos, the ones that re-activated all had show_from dates, server was being clever. On Tue, Dec 6, 2011 at 9:21 PM, Reinier Balt <[email protected]> wrote: > > Currently I add a remote_id column to the local tables which starts blank > for locally added records > > and gets populated during sync, and I think I'd have to stop deleting > rows > and change to using a 'deleted' > > state. For the api I'm dumping the entire thing with xml_export and then > adding/modifying/deleting > > as necessary (not very efficient, but todos.xml only returns active > todos?). > > You can get active todos, completed todos, etc. using the API, see the REST > API documentation in your ?-menu > > Reinier > > > >
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
