This may be fairly minor, but in 0.6.0 while changes to tasks are synced, changes to positions (which Wunderlist tracks as a separate model) are not. There may be two possible solutions to this:
Add a Position model rather than attempting to apply positions as a numeric order on the task level. Automatically join into Positions when loading tasks to gather the correct order. That would allow positions to be properly revisioned and synced but may introduce extra overhead.
Use a concatenation of the task revision and order (e.g. 2-195 revision 2 position 195) as the revision for the Task model. This requires no changes to the database schema unlike the other solution but may become problematic later. Furthermore it may be possible to avoid syncing positions when only task metadata was updated, or vice-versa.
This may be fairly minor, but in 0.6.0 while changes to tasks are synced, changes to positions (which Wunderlist tracks as a separate model) are not. There may be two possible solutions to this:
Add a Position model rather than attempting to apply positions as a numeric order on the task level. Automatically join into Positions when loading tasks to gather the correct order. That would allow positions to be properly revisioned and synced but may introduce extra overhead.
Use a concatenation of the task revision and order (e.g.
2-195
revision2
position195
) as the revision for the Task model. This requires no changes to the database schema unlike the other solution but may become problematic later. Furthermore it may be possible to avoid syncing positions when only task metadata was updated, or vice-versa.