I'm doing a taskwarrior integration utilizing tasklib and there are UDAs in play. UDAs of type date and duration. They're represented as Python strings when acquired task["my_uda"], but I don't think this has to be the case - they could come out as datetime and timedelta IMO. Right now I'm parsing them manually in my integration, but actually this could be implemented in tasklib.
I'd be up for the job, however would like to first consult with some more experienced with the codebase - does it seem like a stupid idea due to architectural concerns or something else?
I'm doing a taskwarrior integration utilizing tasklib and there are UDAs in play. UDAs of type
dateandduration. They're represented as Python strings when acquiredtask["my_uda"], but I don't think this has to be the case - they could come out asdatetimeandtimedeltaIMO. Right now I'm parsing them manually in my integration, but actually this could be implemented in tasklib.I'd be up for the job, however would like to first consult with some more experienced with the codebase - does it seem like a stupid idea due to architectural concerns or something else?