todotxt/todo.txt-cli

Allow for arbitrary addons to be in subdirectories

Open

#214 opened on Aug 19, 2017

View on GitHub
 (2 comments) (0 reactions) (2 assignees)Shell (3,652 stars) (565 forks)batch import
enhancementhelp wanted

Description

It would be great to have action\PLUGIN_NAME\* as a structure so actions (add-ons) can be added in a clean structure without polluting the folder. Right now (after #120), only action/NAME/NAME is supported.

Personally, I use git submodule to structure the actions folder.

An example of something like this is how vim does plugins. See: vim-plug

Contributor guide

Tech stack
shell
Domain
cli
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
familiarity with shell scriptingunderstanding of todo.txt cli addon structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue requests extending the addon loading mechanism to support arbitrary subdirectory structures (e.g., action/PLUGIN NAME/*). Currently, only action/NAME/NAME is supported after PR #120. To implement this, examine the shell script that locates and loads addon actions, likely in the main todo.sh file. The change should allow addons to reside in a subdirectory under action/ with a different naming pattern. Review the existing logic and modify it to iterate over subdirectories. Also consider backward compatibility with the existing structure.