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

Add tags option #94

Merged

Conversation

coddingtonbear
Copy link
Collaborator

NOTE: Don't merge this until you have merged #93 please (it should clear up the PR diff automatically once you've merged).

  • Adds add_tags service property that will automatically add specified tasks.

Additional changes:

  • Read configuration file in as utf-8 bytes (to allow one to specify tags having unicode characters).
  • Altered task diff comparison to be more robust.
  • Cleaned-up private _get_taskwarrior_record method well enough to make it public.

coddingtonbear and others added 30 commits March 4, 2014 19:25
* IssueService subclasses return generators (rather than lists)
* Issue subclasses exist
  * Encapsulating full foreign records, and logic for transforming
    records into taskwarrior's format is deferred to those classes.
  * Transform into taskwarrior's format via a `to_taskwarrior` method.
  * Support dictionary operations and operators to minimize changes
    to related APIs.
  * Define UDAs specific to the underlying API.
  * Define a unique key referencing a combination of any taskwarrior
    record attributes (including UDAs) for deduplicating records and
    associating said records with the underlying API.
* Issue subclasses define UDAs used by the foreign API.
* Issue subclasses define a foreign API key used for relating this
  unique issue with
* Multiprocessing has been altered to receive new issues via a queue.
…ingle failure.

* Required switching sentinel values to integers -- since the objects
  are pickled when being pushed onto the queue, the value popped off
  of the queue will *not* be the same object.  Sad.
* When any single service fails, abort processing for all to avoid
  marking tasks handled by failed services as 'done'.
.json is a bound method.  Calling it is not safe during error handling.
…that are not completed; move managed task gathering into a separate function.
@ralphbean
Copy link
Collaborator

Looks good!

ralphbean added a commit that referenced this pull request Mar 7, 2014
@ralphbean ralphbean merged commit 64e6b26 into GothenburgBitFactory:develop Mar 7, 2014
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 this pull request may close these issues.

2 participants