taskai-cli 1.9.26__tar.gz → 1.10.0__tar.gz

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/CHANGELOG.md

@@ -6,6 +6,30 @@ history. Versions before 1.6.6 predate this file and aren't reconstructed
 here in detail — see `DEVLOG.md` for the full engineering history back to
 the project's start.
 
+## [1.10.0] - Unreleased
+
+CLI expansion.
+
+### Added
+- A dedicated command for every item field: `task due 10 tomorrow`,
+  `task description 10 ...`, `task priority`, `task color` (`task status`
+  already existed). The value needn't be quoted, and leaving it off clears
+  the field. `task name` is now an alias for `task rename`.
+- `task description {id|name} -a {text}` appends to the existing description
+  (on a new line) instead of replacing it
+
+- `task show` draws an item in its `color` (the same per-item color the
+  browser view uses), overriding the `DISPLAY_COLORS` columns for that item
+
+### Changed
+- The CLI shows dates as just the day, `MM/DD/YY` (due dates, `created_on`,
+  comment timestamps) - the time of day is no longer displayed
+- `due_by` is now just `due` everywhere: `--due`, `task show 'due<...'`, the
+  `DISPLAY_STRING` attribute, and the item JSON. Existing databases upgrade
+  themselves on load - a stored `due_by` is read in as `due` (only when `due`
+  isn't already set) and written back out under the new name, and a saved
+  `DISPLAY_STRING` that names `due_by` is rewritten too.
+
 ## [Unreleased]
 
 The v1 release polish pass — see `PHASE_1_RELEASE.md` for the full working

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/DEVPLAN.md

@@ -19,7 +19,7 @@ generic tree node: `parent_id` + `child_ids` form the hierarchy (a root item
 has `parent_id = None`); any item can be a parent of any other item to any
 depth, and the same node type is used whether it's acting as a "list" or a
 "task." Other `TodoItem` fields: `dependency_ids` (blocks-on), `linked_ids`
-(soft link, not reparenting), `comment_ids`, `due_by`, `priority`, `status`,
+(soft link, not reparenting), `comment_ids`, `due`, `priority`, `status`,
 `completed`, `description`, and unused-so-far recurrence fields
 (`recurs_every`/`recurs_until`/`recur_keep_incomplete`). `Comment` is a
 simple `{content, item_id, created_on}`. `UserData` is the whole-DB

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: taskai-cli
-Version: 1.9.26
+Version: 1.10.0
 Author-email: Alex Paskal <alexcpaskal@gmail.com>
 Requires-Python: >=3.12
 Requires-Dist: fastapi>=0.141.1
@@ -55,7 +55,8 @@ task link <parent> <item>         soft-link an item under a second parent
 task unlink <parent> <item>       remove a soft-link
 task reorder <id1> before|after <id2>
 
-task status <id> <text>           set a status string
+task <field> <id> <value>         set one field: description, due, priority, status, color
+                                  (leave the value off to clear it)
 task pomo <on_mins> <off_mins>    pomodoro timer
 
 task ai <prompt>                  natural language → commands
@@ -81,10 +82,11 @@ Pass any of these as `--field value` to `create`, `add`, or `update`:
 | Field | Format | Example |
 |---|---|---|
 | `description` | string | `--description "needs review"` |
-| `due_by` | MM-DD-YYYY | `--due_by 08-15-2026` |
+| `due` | MM-DD-YYYY | `--due 08-15-2026` |
 | `priority` | integer | `--priority 2` |
 | `status` | string | `--status "in progress"` |
 | `completed` | bool | `--completed true` |
+| `color` | CSS color | `--color "#ff8844"` |
 
 ---
 
@@ -154,7 +156,7 @@ task create "Launch website"
 # add subtasks (by name or id)
 task add "Launch website" "Write copy"
 task add "Launch website" "Design mockups" --priority 1
-task add "Launch website" "Set up hosting" --due_by 08-15-2026
+task add "Launch website" "Set up hosting" --due 08-15-2026
 
 # check your work
 task show "Launch website"

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/README.md

@@ -42,7 +42,8 @@ task link <parent> <item>         soft-link an item under a second parent
 task unlink <parent> <item>       remove a soft-link
 task reorder <id1> before|after <id2>
 
-task status <id> <text>           set a status string
+task <field> <id> <value>         set one field: description, due, priority, status, color
+                                  (leave the value off to clear it)
 task pomo <on_mins> <off_mins>    pomodoro timer
 
 task ai <prompt>                  natural language → commands
@@ -68,10 +69,11 @@ Pass any of these as `--field value` to `create`, `add`, or `update`:
 | Field | Format | Example |
 |---|---|---|
 | `description` | string | `--description "needs review"` |
-| `due_by` | MM-DD-YYYY | `--due_by 08-15-2026` |
+| `due` | MM-DD-YYYY | `--due 08-15-2026` |
 | `priority` | integer | `--priority 2` |
 | `status` | string | `--status "in progress"` |
 | `completed` | bool | `--completed true` |
+| `color` | CSS color | `--color "#ff8844"` |
 
 ---
 
@@ -141,7 +143,7 @@ task create "Launch website"
 # add subtasks (by name or id)
 task add "Launch website" "Write copy"
 task add "Launch website" "Design mockups" --priority 1
-task add "Launch website" "Set up hosting" --due_by 08-15-2026
+task add "Launch website" "Set up hosting" --due 08-15-2026
 
 # check your work
 task show "Launch website"

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/docs/_static/demo-script.md

@@ -15,7 +15,7 @@ and the tree is uncluttered.
 
 ```bash
 task create "Launch blog"
-task add "Launch blog" "Write outline" --priority 1 --due_by tomorrow
+task add "Launch blog" "Write outline" --priority 1 --due tomorrow
 task next "Write outline" "Draft intro"
 task show all
 task done "Write outline"
@@ -25,7 +25,7 @@ task show all
 
 What this covers, in order:
 1. `create`/`add` — the everything-is-an-item tree, with a couple of fields
-   set (`--priority`, `--due_by tomorrow` — also shows off the relative
+   set (`--priority`, `--due tomorrow` — also shows off the relative
    date keyword)
 2. `next` — chains, the newest major feature, right after the tree basics
 3. `show all` — the Rich-rendered tree, chain included (rendered inline

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/docs/browser-mode.md

@@ -19,7 +19,7 @@ Double-click a card to center on it and open its edit panel.
 - **Completed** items are tinted green.
 - **`status`** text appears in the top corner of a card (or the color set by
   `STATUS_COLORS` in config, if one's configured for that status).
-- **`due_by`**, if set, appears in the bottom corner.
+- **`due`**, if set, appears in the bottom corner.
 - **Soft links** (`task link`) are drawn as a dashed copy of the linked item
   under its host, distinct from the solid parent/child connectors.
 - **Chains** (`task next`/`task chain`) render as a straight bold arrow; a

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/docs/configuration.md

@@ -20,13 +20,15 @@ task config pop <key>      # remove a key; it returns to its default
 
 `DISPLAY_STRING`
 : Space-separated list of item attributes shown per row by `task show`.
-  Default: `id name status due_by`.
+  Default: `id name status due`.
 
 `DISPLAY_COLORS`
 : Space-separated colors, matched position-for-position to `DISPLAY_STRING`.
   Use `_` to leave a column uncolored. Default: `_ white dark_orange _`.
+  An item with its own [`color`](item-data.md) set is drawn entirely in that
+  color instead, whatever these say.
 
 ```bash
-task config set DISPLAY_STRING "id name priority due_by"
+task config set DISPLAY_STRING "id name priority due"
 task config set DISPLAY_COLORS "_ white cyan _"
 ```

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/docs/getting-started.md

@@ -59,7 +59,7 @@ Every item is a tree node. Start with a root item, then hang children off it.
 Names with spaces must be quoted.
 
 ```bash
-task create "Launch blog" --due_by 09-15-2026
+task create "Launch blog" --due 09-15-2026
 task add "Launch blog" "Write first post" --priority 1
 task add "Launch blog" "Set up hosting"
 task add "Write first post" "Draft outline"

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/docs/index.md

@@ -15,7 +15,7 @@ A command-line task manager with AI features.
   items at any depth; there's no separate notion of "lists"
 - **Attach data to each item** — description, due date, priority, status,
   completion, comments
-- **Filter** — `task show 'priority>=2' 'due_by<10-01-2026'` narrows the tree to
+- **Filter** — `task show 'priority>=2' 'due<10-01-2026'` narrows the tree to
   matching items and their parents
 - **Soft-link** an item under more than one parent without moving it
 - **Interactive mode** — run `task` with no arguments for a live view that

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/docs/item-data.md

@@ -5,25 +5,48 @@ fields. Set them as named options — `--<name> <value>` — on `task create`,
 `task add`, and `task update`:
 
 ```bash
-task create "Ship v2" --due_by 10-01-2026 --priority 2
+task create "Ship v2" --due 10-01-2026 --priority 2
 task update "Ship v2" --status "in progress" --description "cut the release branch first"
 ```
 
 | Option | Value | Meaning |
 |---|---|---|
 | `--description` | text | A longer note on the item. Quote it if it has spaces. |
-| `--due_by` | `MM-DD-YYYY` | When the item is due. |
+| `--due` | `MM-DD-YYYY` | When the item is due. |
 | `--priority` | integer | A number you choose; sort or filter by it. Default `0`. |
 | `--status` | text | A free-form state such as `blocked` or `in review`. Shown on the node in the browser view. |
 | `--completed` | `true` / `false` | Whether the item is done. |
+| `--color` | a CSS color, e.g. `"#ff8844"` or `green` | Fills the item's card in the browser view, and draws its whole line in `task show` in that color (overriding the `DISPLAY_COLORS` columns). |
 
 ## Dedicated commands
 
-Some changes have their own command instead of an option:
+Every field above also has its own command, so you can skip `update` and the
+`--` for the common case:
+
+```bash
+task due 4 tomorrow                 # same as: task update 4 --due tomorrow
+task priority 4 2
+task status 4 "in review"
+task color 4 "#ff8844"
+task description 4 needs a rewrite  # the value needn't be quoted
+task due 4                          # no value clears the field
+```
+
+The value is everything after the item, so multi-word text and dates like
+`task due 4 Dec 31 2026` work without quotes.
+
+`task description` takes an `-a` flag to append to the existing description
+(on a new line) instead of replacing it:
+
+```bash
+task description 4 first draft outline
+task description 4 -a also cover the hosting options
+```
+
+A few other changes have their own command too:
 
 ```bash
 task rename 4 "Ship v2.1"
-task status 4 "in review"           # same as --status, as its own verb
 task comment 4 "waiting on QA sign-off"
 task complete 4                     # mark item 4 done
 task done 4                         # alias for complete

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/docs/managing-the-tree.md

@@ -21,7 +21,7 @@ already exists — give the parent first, then the new item's name. Both accept
 [item data](item-data.md) as named options:
 
 ```bash
-task add "Launch blog" "Set up hosting" --due_by 09-30-2026 --priority 1
+task add "Launch blog" "Set up hosting" --due 09-30-2026 --priority 1
 ```
 
 ## View items
@@ -40,11 +40,11 @@ the items matching *all* of them, each with its parent chain for context:
 ```bash
 task show 'name=Write*'                     # = on text is a glob match
 task show 'priority>=2' 'completed=false'
-task show 'status=in review' 'due_by<10-01-2026'
+task show 'status=in review' 'due<10-01-2026'
 ```
 
 Operators are `=`, `>`, `<`, `>=`, `<=`. Text fields (`name`, `description`,
-`status`) glob-match on `=`; `priority`, `due_by`, `created_on`, and `id`
+`status`) glob-match on `=`; `priority`, `due`, `created_on`, and `id`
 compare numerically / by date. Put no space around the operator, and quote each
 test so your shell doesn't treat `>` and `<` as redirects.
 

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "taskai-cli"
-version = "1.9.26"
+version = "1.10.0"
 description = ""
 authors = [{name = "Alex Paskal", email = "alexcpaskal@gmail.com"}]
 readme = "README.md"

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/taskai/cli.py

@@ -113,9 +113,9 @@ class Controller:
                         kwargs["completed"] = v
                     else:
                         kwargs["completed"] = str(v).strip().lower() in ("true", "1", "yes")
-                case "due_by":
+                case "due":
                     if isinstance(v, str):
-                        kwargs["due_by"] = parse_date_value(v)
+                        kwargs["due"] = parse_date_value(v)
                 case "depends_on":
                     # CLI-facing alias for the model's dependency_ids field;
                     # accepts a comma-separated id list ("1,2,3") or one id
@@ -207,6 +207,25 @@ class Controller:
 
         db.commit()
 
+    def set_attribute(item_id: int|str, attr: str, value: str = "", append: bool = False):
+        """Backs the dedicated `task <attr> {id|name} {value}` commands: set
+        one item field. An empty value clears it back to the field's default
+        (no due date, priority 0, no color, ...). With `append` (description
+        only) the value goes on a new line after the existing text instead of
+        replacing it."""
+        if append:
+            if attr != "description":
+                Controller.throw_error(f"-a only applies to description, not {attr}")
+            if value == "":
+                Controller.throw_error("nothing to append - give the text to add")
+            item = Controller._resolve_item(item_id)
+            item_id = item.id
+            if item.description.strip():
+                value = f"{item.description.rstrip()}\n{value}"
+        elif value == "":
+            value = TodoItem.model_fields[attr].default
+        Controller.update_item(item_id, **{attr: value})
+
     def delete_item(id_: int|str, chain: bool = False):
         item = Controller._resolve_item(id_)
 
@@ -596,9 +615,20 @@ def execute_commands(*args, **kwargs) -> int:
             case "move":
                 Controller.move_item(args[1], args[2])
 
-            case "rename":
+            case "rename" | "name":
                 Controller.update_item(args[1], name=args[2])
 
+            # one dedicated command per item field: `task due 10 tomorrow`.
+            # The value is everything after the item, so it needn't be quoted
+            # (`task description 10 needs a rewrite`); leaving it off clears
+            # it, and `description -a` appends to the existing text instead
+            case "description" | "due" | "priority" | "color" | "status":
+                append = "-a" in args
+                words = [a for a in args[1:] if a != "-a"]
+                if not words:
+                    Controller.throw_error(f"usage: task {args[0]} {{id|name}} {{value}}")
+                Controller.set_attribute(words[0], args[0], " ".join(words[1:]), append=append)
+
             case "pomo":
                 pomodoro_service(int(args[1]), int(args[2]))
 
@@ -607,13 +637,6 @@ def execute_commands(*args, **kwargs) -> int:
                 import orjson as json
                 print_json(json.dumps(db.get_item(int(args[1])).model_dump()).decode())
 
-            case "status":
-                if len(args) < 3:
-                    item_id, status_val = args[1], ""
-                else:
-                    item_id, status_val = args[1:3]
-                Controller.update_item(item_id, status=status_val)
-
             case "exit" | "exit()" | "quit":
                 return 0
 

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/taskai/dates.py

@@ -1,7 +1,7 @@
 """Shared due-date parsing: a couple of relative keywords plus a handful of
-common formats, tried in turn. Used by both the CLI's --due_by/create/
+common formats, tried in turn. Used by both the CLI's --due/create/
 update path (cli.py's _parse_item_kwargs) and date-attribute filter values
-(filters.py's due_by/created_on) so the two don't drift apart.
+(filters.py's due/created_on) so the two don't drift apart.
 """
 
 from datetime import datetime, timedelta

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/taskai/filters.py

@@ -1,7 +1,7 @@
 """
 Attribute filters for `task show`.
 
-    task show status="IN PROGRESS" priority>=2 due_by<12-31-2026
+    task show status="IN PROGRESS" priority>=2 due<12-31-2026
 
 Each argument is one filter, `attr<op>value`, with no spaces around the
 operator (a quoted value with spaces still arrives as a single token). Every
@@ -23,7 +23,7 @@ from taskai.json_dir_database import DatabaseError
 
 # attr -> how both sides of the comparison should be read
 _INT_ATTRS = {"id", "parent_id", "priority"}
-_DATE_ATTRS = {"due_by", "created_on"}
+_DATE_ATTRS = {"due", "created_on"}
 _BOOL_ATTRS = {"completed"}
 _STR_ATTRS = {"name", "description", "status"}
 

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/taskai/help_menu.py

@@ -15,8 +15,8 @@ Viewing:
 'task show {attr}{op}{value} ...' --> show only items matching every filter, each with its parent chain for context
   ops: = > < >= <= ; text uses = with fnmatch (name=Write*), the rest compare numbers/dates
   no spaces around the operator; quote each expression so your shell doesn't treat > < as redirects
-  e.g. task show 'status=IN PROGRESS' 'priority>=2' 'due_by<12-31-2026'
-  due_by/created_on also accept the keywords today/tomorrow, e.g. 'due_by=today', 'due_by<tomorrow'
+  e.g. task show 'status=IN PROGRESS' 'priority>=2' 'due<12-31-2026'
+  due/created_on also accept the keywords today/tomorrow, e.g. 'due=today', 'due<tomorrow'
 
 Creating:
 'task create {name} {--field value ...}' --> create a new top-level (root) item - use this when there's no existing parent to attach to
@@ -25,7 +25,10 @@ Creating:
 Modifying items (an id or a name works everywhere):
 'task update {id|name} {--field value ...}' --> update fields on an item
 'task rename {id|name} {new name}' --> rename an item
-'task status {id|name} {text}' --> set an item's status string
+'task {field} {id|name} {value}' --> set one item field with its own command; field is one of description, due, priority, status, color
+  e.g. task due 10 tomorrow / task priority 10 2 / task status 10 "in review" / task color 10 "#ff8844"
+  the value needn't be quoted (task description 10 needs a rewrite); leave it off to clear the field (task due 10)
+  task description {id|name} -a {text} --> append text to the existing description, on a new line, instead of replacing it
 'task comment {id|name} {text}' --> add a comment to an item
 'task complete {id|name}' / 'task done {id|name}' --> mark an item complete; add -r (or -recursive) to also complete all its descendants
 'task undone {id|name}' --> mark an item not complete; add -r (or -recursive) to also un-complete all its descendants
@@ -50,10 +53,11 @@ Deleting:
 
 Item fields (pass as named options, e.g. --priority 2, to create/add/update):
   description  string
-  due_by       MM-DD-YYYY, YYYY-MM-DD, MM/DD/YYYY, "Dec 31, 2026", or the keywords today/tomorrow
+  due          MM-DD-YYYY, YYYY-MM-DD, MM/DD/YYYY, "Dec 31, 2026", or the keywords today/tomorrow
   priority     integer
   status       string
   completed    true|false
+  color        a CSS color such as #ff8844 or green - fills the item's card in the browser and colors its whole line in `task show`
 
 AI:
 'task ai {prompt}' --> feed a prompt to an LLM, which converts it into a series of the commands above and runs them
@@ -84,7 +88,7 @@ help_examples = """
 Worked examples - copy/paste and adapt. Names with spaces must be quoted.
 
 Build a small project tree:
-  task create "Launch blog" --due_by 09-15-2026
+  task create "Launch blog" --due 09-15-2026
   task add "Launch blog" "Write first post" --priority 1
   task add "Launch blog" "Set up hosting"
   task add "Write first post" "Draft outline"
@@ -92,6 +96,10 @@ Build a small project tree:
 
 Work an item and finish it:
   task status 4 "in progress"
+  task due 4 tomorrow               # every item field has a command like this
+  task priority 4 2
+  task description 4 first draft outline
+  task description 4 -a "also cover the hosting options"   # -a appends instead of replacing
   task comment 4 "stuck on the intro paragraph"
   task done 4                       # completes just item 4
   task done 4 -r                    # completes item 4 and everything under it

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/taskai/json_dir_database.py

@@ -23,6 +23,30 @@ def _is_chain_head(item: TodoItem) -> bool:
     return item.prev_chain_id is None and item.next_chain_id is not None
 
 
+def _migrate_legacy_keys(user_data: UserData) -> None:
+    """Backwards compatibility for data written before `due_by` became `due`.
+
+    Runs once per load, right after the file is read, so everything
+    downstream - raw-dict reads like get_item_attr included - only ever sees
+    the current names; the next commit writes them back out under the new
+    ones. A legacy `due_by` only fills in `due` when it has a value and `due`
+    doesn't, and the legacy key is dropped either way so it can't linger.
+    """
+    for item in user_data.todo_items.values():
+        if "due_by" in item:
+            legacy_due = item.pop("due_by")
+            if legacy_due and not item.get("due"):
+                item["due"] = legacy_due
+
+    # a saved DISPLAY_STRING can name the old attribute too (the default
+    # used to, and `task config set` persists every default it fills in)
+    display_string = user_data.config.get("DISPLAY_STRING")
+    if display_string:
+        user_data.config["DISPLAY_STRING"] = " ".join(
+            "due" if attr == "due_by" else attr for attr in display_string.split(" ")
+        )
+
+
 class JsonDirectoryDatabase:
     """
     All views extracted from the database are read only
@@ -59,6 +83,7 @@ class JsonDirectoryDatabase:
                     )
                 else:
                     self.user_data = UserData(**json.loads(json_bstring))
+                    _migrate_legacy_keys(self.user_data)
         else:
             raise DatabaseError("Database already connected")
 

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/taskai/models.py

@@ -36,7 +36,7 @@ class TodoItem(Base):
     created_on: datetime = Field(default_factory=datetime.now)
     completed: bool = False
     description: str = ""
-    due_by: Optional[datetime] = None
+    due: Optional[datetime] = None
     comment_ids: list[int] = Field(default_factory=list)
     dependency_ids: list[int] = Field(default_factory=list)
     linked_ids: list[int] = Field(default_factory=list)
@@ -73,7 +73,7 @@ class CLIConfig(Base):
     AI_MODEL: Optional[str] = None
 
     # VIEW
-    DISPLAY_STRING: str = "id name status due_by"
+    DISPLAY_STRING: str = "id name status due"
     DISPLAY_COLORS: str = "_ white dark_orange _"
     # per-status-string color for the DAG node's status label, e.g.
     # "RUNNING=green,BLOCKED=red" - browser-only today (CLI status display

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/taskai/static/editpanel.js

@@ -25,7 +25,7 @@ function isoToDateInputValue(iso) {
 }
 
 // "YYYY-MM-DD" (native <input type="date"> value) -> "MM-DD-YYYY", matching
-// the CLI's documented --due_by format
+// the CLI's documented --due format
 function dateInputValueToCliFormat(value) {
 	const [year, month, day] = value.split("-");
 	return `${month}-${day}-${year}`;
@@ -42,7 +42,7 @@ const FIELD_DEFS = [
 	// but an empty string here correctly means "no override, use the default"
 	{ key: "color", label: "Color", type: "text" },
 	{ key: "priority", label: "Priority", type: "number" },
-	{ key: "due_by", label: "Due by", type: "date", format: isoToDateInputValue },
+	{ key: "due", label: "Due", type: "date", format: isoToDateInputValue },
 	{ key: "completed", label: "Completed", type: "checkbox" },
 	// description goes last and is flagged `grow`: it's the big free-text
 	// field, so it sits at the bottom and stretches to fill whatever panel
@@ -102,8 +102,8 @@ function handleFieldChange(item, def, value, immediate = false) {
 		return;
 	}
 
-	if (def.key === "due_by") {
-		if (!value) return; // clearing due_by isn't supported by the CLI today
+	if (def.key === "due") {
+		if (!value) return; // clearing due isn't supported by the CLI today
 		value = dateInputValueToCliFormat(value);
 	}
 

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/taskai/static/graph.js

@@ -52,7 +52,7 @@ function buildTree(itemsById, id, seen = new Set()) {
 		size: STYLE.node.size,
 		completed: item.completed,
 		status: item.status,
-		due_by: item.due_by,
+		due: item.due,
 		color: item.color,
 		children,
 	};

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/taskai/static/navigation.js

@@ -2,10 +2,11 @@
 // direction key moves to. Every direction has exactly one meaning, with no
 // fallbacks:
 //   - a plain (non-chain) node: down/up are children/parent, as ever
-//   - a chain member: down/up are chainNext/chainPrev — the chain is the
+//   - a chain member: down is chainNext, up is chainPrev — the chain is the
 //     spine you walk, and its side subtrees are never entered by accident.
-//     The one exception is up from the head of a chain that sits at the top
-//     level of the forest, which goes to the synthetic root (show all)
+//     A chain's head has no chainPrev, so up from it leaves the chain for the
+//     head's tree parent (the synthetic root, i.e. show all, for a top-level
+//     chain)
 //   - into: chain member -> its subtree (remembered/first child), else nothing
 //   - out: jump to the nearest chain member whose subtree contains the
 //     current node (starting from the head of the node's own chain, if it's
@@ -49,10 +50,11 @@ function navigateGraph(direction, cur, graph) {
 	if (direction === "down") {
 		target = inChain ? cur.chainNext : rememberedChild(cur);
 	} else if (direction === "up") {
-		// only a chain's head has a parent - a top-level one is the synthetic root
-		target = inChain
-			? cur.chainPrev || (cur.parent === graph.rootNode ? graph.rootNode : null)
-			: cur.parent;
+		// a node has either a chainPrev (a non-head chain member) or a tree
+		// parent (a chain's head, or any plain node), never both, so this never
+		// has to choose: walk back along the chain, and from its head leave it
+		// for the tree parent (the synthetic root for a top-level chain)
+		target = cur.chainPrev || cur.parent;
 	} else if (direction === "into") {
 		target = inChain ? rememberedChild(cur) : null;
 	} else if (direction === "out") {

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/taskai/static/render.js

@@ -238,13 +238,13 @@ function drawNode(ctx, node, isHovered, isSelected) {
 		ctx.fillText(statusLabel, nodeX + node.size - STYLE.node.idPadding, nodeY + STYLE.node.idPadding);
 	}
 
-	if (!isShadow && node.due_by) {
+	if (!isShadow && node.due) {
 		ctx.fillStyle = STYLE.colors.dueText;
 		ctx.font = STYLE.node.idFont;
 		ctx.textAlign = "right";
 		ctx.textBaseline = "bottom";
 		// "2026-12-31T00:00:00" -> "12/31" - compact, locale-agnostic
-		const dueLabel = node.due_by.slice(5, 7) + "/" + node.due_by.slice(8, 10);
+		const dueLabel = node.due.slice(5, 7) + "/" + node.due.slice(8, 10);
 		ctx.fillText(dueLabel, nodeX + node.size - STYLE.node.idPadding, nodeY + node.size - STYLE.node.idPadding);
 	}
 

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/taskai/views.py

@@ -1,3 +1,6 @@
+# standard lib
+from datetime import datetime
+
 # local
 from taskai.json_dir_database import JsonDirectoryDatabase, DatabaseError
 from taskai.models import TodoItem, Comment
@@ -5,6 +8,7 @@ from taskai.config import config
 
 # external
 from rich import print
+from rich.color import Color, ColorParseError
 from rich.console import Console
 
 
@@ -26,7 +30,7 @@ VALID_ATTRS = {
     "id",
     "name",
     "created_on",
-    "due_by",
+    "due",
     "priority",
     "status"
 }
@@ -61,13 +65,16 @@ def view_lists(
 
     def _render_display_string(item: TodoItem):
         display_string = ""
+        item_color = _rich_color(item.color)
         for i, attr in enumerate(attrs):
             part = getattr(item, attr)
             if not part:
                 continue
-            part = str(part)
-            if display_colors and colors[i] != "_":
-                part = _wrap_string(part, f"[{colors[i]}]", f"[/{colors[i]}]")  
+            part = _format_date(part) if isinstance(part, datetime) else str(part)
+            # an item's own color beats the column colors: it's drawn entirely in it
+            color = item_color or (colors[i] if display_colors and colors[i] != "_" else None)
+            if color:
+                part = _wrap_string(part, f"[{color}]", f"[/{color}]")  
             display_string += f" {part}"
         display_string = _wrap_string(display_string, "[strike]", "[/strike]", condition=item.completed)
         return display_string
@@ -131,9 +138,11 @@ def view_item(
     item = db.get_item(item_id)
 
     console = Console()
-    console.print(f"[bold green]Name:[/bold green] {item.name}")
-    if item.due_by:
-        console.print(f"[bold green]Due By:[/bold green] {item.due_by or ""}")
+    item_color = _rich_color(item.color)
+    name = _wrap_string(item.name, f"[{item_color}]", f"[/{item_color}]", condition=bool(item_color))
+    console.print(f"[bold green]Name:[/bold green] {name}")
+    if item.due:
+        console.print(f"[bold green]Due:[/bold green] {_format_date(item.due)}")
     
     if item.description:
         console.print(f"\n[bold green]Description:[/bold green]\n{item.description}")
@@ -142,7 +151,7 @@ def view_item(
         console.print("\n[bold green]\nComments:[/bold green]")
         for comment_id in item.comment_ids:
             comment: Comment = db.get_comment(comment_id)
-            console.print(f"{comment.created_on.strftime("%Y-%m-%d %H:%M:%S")} - {comment.content}")
+            console.print(f"{_format_date(comment.created_on)} - {comment.content}")
     
     if item.child_ids:
         console.print("\n[bold green]\nSubtasks:[/bold green]")
@@ -158,6 +167,40 @@ def view_item(
 
 ### Utils
 
+# CSS color names Rich has no name for (its named colors come from the 256-color
+# ANSI palette), so an item colored "orange" in the browser can still be shown
+_CSS_COLORS_MISSING_IN_RICH = {
+    "orange": "#ffa500", "pink": "#ffc0cb", "gold": "#ffd700", "teal": "#008080",
+    "brown": "#a52a2a", "indigo": "#4b0082", "violet": "#ee82ee", "crimson": "#dc143c",
+    "coral": "#ff7f50", "salmon": "#fa8072", "lime": "#00ff00", "olive": "#808000",
+    "navy": "#000080", "maroon": "#800000", "silver": "#c0c0c0", "gray": "#808080",
+    "grey": "#808080",
+}
+
+
+def _rich_color(css_color: str | None) -> str | None:
+    """An item's `color` (a CSS color string, e.g. "#ff8844" or "green") as a
+    Rich color, or None when it's unset or isn't one Rich can draw - an
+    unusable color just isn't shown rather than breaking the whole listing."""
+    if not css_color:
+        return None
+    css_color = css_color.strip().lower()
+    for candidate in (css_color, _CSS_COLORS_MISSING_IN_RICH.get(css_color)):
+        if not candidate:
+            continue
+        try:
+            Color.parse(candidate)
+        except ColorParseError:
+            continue
+        return candidate
+    return None
+
+
+def _format_date(value: datetime) -> str:
+    """How every date is shown in the CLI: just the day, MM/DD/YY - the time
+    of day is never displayed."""
+    return value.strftime("%m/%d/%y")
+
 
 def _wrap_string(string_, before, after=None, condition=True):
     if after is None:

taskai_cli-1.10.0/test/test_legacy_migration.py

@@ -0,0 +1,73 @@
+import sys, os; sys.path.append(os.getcwd())
+import shutil
+
+import orjson as json
+
+from taskai.json_dir_database import JsonDirectoryDatabase
+
+LEGACY_DIR = "_tmp_legacy_dir"
+
+
+def _write_legacy_file(items: dict, config: dict | None = None):
+    os.makedirs(LEGACY_DIR, exist_ok=True)
+    data = {"name": "test_user", "id_counter": len(items), "todo_items": items, "config": config or {}}
+    with open(os.path.join(LEGACY_DIR, "test_user.json"), "wb") as f:
+        f.write(json.dumps(data))
+
+
+def _connect() -> JsonDirectoryDatabase:
+    db = JsonDirectoryDatabase(LEGACY_DIR, "test_user")
+    db.connect()
+    return db
+
+
+def _cleanup():
+    if os.path.exists(LEGACY_DIR):
+        shutil.rmtree(LEGACY_DIR)
+
+
+def test_due_by_is_read_as_due():
+    _cleanup()
+    try:
+        _write_legacy_file({
+            "1": {"id": 1, "name": "old", "due_by": "2026-10-01T00:00:00"},
+            "2": {"id": 2, "name": "no due", "due_by": None},
+            "3": {"id": 3, "name": "both", "due_by": "2026-01-01T00:00:00", "due": "2026-02-02T00:00:00"},
+        })
+        db = _connect()
+
+        assert db.get_item(1).due.isoformat() == "2026-10-01T00:00:00"
+        assert db.get_item(2).due is None
+        # `due` wins when both are set - the legacy key never overwrites it
+        assert db.get_item(3).due.isoformat() == "2026-02-02T00:00:00"
+
+        # raw-dict reads see the new name too, and the legacy key is gone
+        assert db.get_item_attr(1, "due") == "2026-10-01T00:00:00"
+        assert all("due_by" not in item for item in db.user_data.todo_items.values())
+    finally:
+        _cleanup()
+
+
+def test_migrated_data_is_written_back_under_the_new_name():
+    _cleanup()
+    try:
+        _write_legacy_file({"1": {"id": 1, "name": "old", "due_by": "2026-10-01T00:00:00"}})
+        db = _connect()
+        db.commit()
+
+        with open(os.path.join(LEGACY_DIR, "test_user.json"), "rb") as f:
+            saved = json.loads(f.read())
+        assert "due_by" not in saved["todo_items"]["1"]
+        assert saved["todo_items"]["1"]["due"] == "2026-10-01T00:00:00"
+    finally:
+        _cleanup()
+
+
+def test_saved_display_string_is_migrated():
+    _cleanup()
+    try:
+        _write_legacy_file({}, config={"DISPLAY_STRING": "id name status due_by"})
+        db = _connect()
+        assert db.get_config().DISPLAY_STRING == "id name status due"
+    finally:
+        _cleanup()

{taskai_cli-1.9.26 → taskai_cli-1.10.0}/test/test_view.py

@@ -24,7 +24,7 @@ def _populate_db():
     child1 = db.create_item(name="child 1", parent_id=root1, priority=3)
     root2 = db.create_item(name="root 2", description="Describe Marcellus Wallace")
     child2 = db.create_item(name="child 2", parent_id=root2, priority=2)
-    child3 = db.create_item(name="child 3", parent_id=root2, due_by=datetime(2026,10, 1))
+    child3 = db.create_item(name="child 3", parent_id=root2, due=datetime(2026,10, 1))
     gchild1 = db.create_item(name="grandchild 1", parent_id=child3, completed=True, description="Say 'what' again.")
     db.create_comment("I dare you", item_id=gchild1)
     db.create_comment("I double dare you mothafucka, say 'what' one more goddamn time", item_id=gchild1)