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

[TW-1938] Adjust behaviour of new-uuid and new-id verbosity levels #1950

Closed
taskwarrior opened this Issue Feb 14, 2018 · 3 comments

Comments

Projects
None yet
1 participant
@taskwarrior
Contributor

taskwarrior commented Feb 14, 2018

Paul Fenwick on 2017-12-04T19:36:34Z says:

In TaskWarrior 2.5 the new-uuid verbosity would provide a UUID on task creation.

This still exists in 2.6, but the new-id verbosity level overrides it.

The attached patches/PR makes the following adjustments:

  • If new-id and new-uuid are both set, new-uuid takes precedence.
  • new-uuid is no longer enabled by default.

This means that scripts that use new-uuid because they want an enduring identifier for a task (eg: Python's 'taskw' module) can continue to use it, but users can get human-friendly integer IDs under normal operation.

In particular, this change fixes a conflict with taskw.py which would cause task creation to fail, as a UUID was expected, but an integer ID was being returned.

Feedback super appreciated. I know in the changelogs it says that new-uuid is now deprecated.

@taskwarrior taskwarrior added this to the 2.6.0 milestone Feb 14, 2018

@taskwarrior

This comment has been minimized.

Contributor

taskwarrior commented Feb 14, 2018

Migrated metadata:

Created: 2017-12-04T19:36:34Z
Modified: 2017-12-10T03:54:00Z
@taskwarrior

This comment has been minimized.

Contributor

taskwarrior commented Feb 14, 2018

Paul Fenwick on 2017-12-04T19:39:15Z says:

Pull request opened: https://git.tasktools.org/TM/task/pulls/2

@taskwarrior

This comment has been minimized.

Contributor

taskwarrior commented Feb 14, 2018

Paul Beckingham on 2017-12-10T03:54:00Z says:

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment