Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task position updates are ignored #123

Open
idpaterson opened this issue Jun 22, 2016 · 2 comments
Open

Task position updates are ignored #123

idpaterson opened this issue Jun 22, 2016 · 2 comments
Labels

Comments

@idpaterson
Copy link
Owner

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.

@idpaterson idpaterson added the bug label Jun 22, 2016
@idpaterson idpaterson added this to the 0.6 milestone Jun 22, 2016
@idpaterson idpaterson self-assigned this Jun 22, 2016
@idpaterson idpaterson removed this from the 0.6 milestone Aug 24, 2016
@idpaterson
Copy link
Owner Author

I think that the better solution is to track Positions separately, the same way that Wunderlist does. This will be revisited in a later version.

@idpaterson idpaterson changed the title Task position updates are ignored in 0.6.0 Task position updates are ignored Aug 30, 2016
@idpaterson
Copy link
Owner Author

List positions do not change, either.

@idpaterson idpaterson removed their assignment Nov 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant