RFC: Support time periods other than days (months, years) about todo.txt-cli-again-addon HOT 3 CLOSED

Sounds like a good feature; one could keep the default behaviour for days, but add support for stepping months or years.

I agree that the BSD behaviour is more desirable when stepping months. A bit trickier to get that one working, but nothing impossible.

from todo.txt-cli-again-addon.

I'm working on implementing this feature right now. For more efficient testing, I found it useful to move some of the helper functions (adjust_date, determine_date_version, and a couple of others) to a separate file which I named againHelpers.sh. I also created a new unitTests.sh file that sources againHelpers.sh and makes several calls to adjust_date, without having to setup dummy tasks in test\sample.txt. My plan is for again to also source againHelpers.sh. Does this violate a design goal of keeping all of the add-on code in a single file?

If it does, my backup plan was to add a flag in again (something like AGAIN_TEST_IN_PROGRESS) and place most of the execution inside of an if block guarded by this flag. testAgain.sh could set the flag (to disable execution) then source again. If you would like to stick to a single file, what are your thoughts regarding this approach?

from todo.txt-cli-again-addon.

I hate code duplication as much as the next developer, and I most certainly do not have some hidden single-file agenda, so if refactoring things into a utility file makes development and testing easier, I'm all for it.

One alternate solution to all of this would, I guess, be to detect modify again in such a way that it detects if it is sourced or not, and provide different behaviour in that case, but I'm not sure if there exists a portable way to detect that.

from todo.txt-cli-again-addon.