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

Make TaskwarriorExperimental the default #30

Closed
kostajh opened this issue Jan 20, 2014 · 4 comments · Fixed by #31
Closed

Make TaskwarriorExperimental the default #30

kostajh opened this issue Jan 20, 2014 · 4 comments · Fixed by #31

Comments

@kostajh
Copy link
Contributor

kostajh commented Jan 20, 2014

Is there a timeline for this? I recently tested a program that used taskw but relied on the method for directly reading task data, which failed. IMO a more stable implementation would be to rely on task export/add/modify/delete for viewing and manipulating task data, as TaskwarriorExperimental does.

@ralphbean
Copy link
Owner

Let's do it now.

@ralphbean
Copy link
Owner

How about we have taskw decide at runtime which implementation is default. If it can find a task binary and if the version is sufficiently advanced, then the TaskWarrior class will use task export/add/modify/delete. If not, then it will fall back to the "old normal".

@kostajh
Copy link
Contributor Author

kostajh commented Jan 20, 2014

That sounds like a good plan to me. I would suggest making 2.3.0 the minimum, since I encountered some problems with task export and UDAs in 2.2.0 and that issue has been fixed in 2.3. I'm not aware of any task export problems in 2.3.0.

@kostajh
Copy link
Contributor Author

kostajh commented Jan 21, 2014

@ralphbean 👍 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants