rc.verbose=new-uuid only works if it is the first paramater for taskwarrior 2.5.2

[EdwardBetts]

There is a bug in version of taskwarrior that the rc.verbose=new-uuid argument will only work if it is the first argument.

See GothenburgBitFactory/taskwarrior#1953

This change moves the 'verbose' config option to be first in DEFAULT_CONFIG_OVERRIDES.

Without this change the test suite fails and it isn't possible to create new tasks.

[coddingtonbear]

Unfortunately, dictionaries aren't ordered by insertion order in Python < 3.7; so I'm afraid this doesn't quite work unless you also change this to be a collections.OrderedDict instance.

[vrusinov]

Python 3.6 support ends in 7 months (23 Dec 2021). So while incomplete, this simple change fixes taskw for majority of supported Python versions.

[jayvdb]

When I use this for the tests on Python 3.8, it lets 37 extra tests pass, but 10 tests still fail.

[EdwardBetts]

@jayvdb: It took me three patches to make taskw build without any test failures.

Patches are here: https://salsa.debian.org/python-team/packages/taskw/-/tree/debian/master/debian/patches

[bergercookie]

I also stumbled upon the same issue and solved it by parsing the ID from stdout instead of the UUID.
It's interesting to note that the verbose.new-uuid is now supported only for TW >= 2.6.0 according to this page:

https://taskwarrior.org/docs/verbosity.html
bergercookie/taskw-ng@8e1235d

[BlackYoup]

Hello, is there anything to do to help get this merged? I believe proposing a different patch according to the review that was emitted?

It's interesting to note that the verbose.new-uuid is now supported only for TW >= 2.6.0 according to this page:

It seems like it's in the code base of v2.5.3 when parsing the verbosity so it may only be a documentation problem? https://github.com/GothenburgBitFactory/taskwarrior/blob/2f47226f91f0b02f7617912175274d9eed85924f/src/Context.cpp#L953

[ralphbean]

Merging in #147.