todo.due-label

export function dueLabel(todo: Todo, today: string): string

import { dueLabel } from "#fune/todo.due-label@^1";

import { parseIsoDate } from "./dates_add_days.ts";  ← from dates.add-days ^1.0.0 · built alongside by fune
import { dayName } from "./dates_day_of_week.ts";  ← from dates.day-of-week ^1.0.0 · built alongside by fune
import { daysBetween } from "./dates_days_between.ts";  ← from dates.days-between ^1.0.0 · built alongside by fune
import { dueStatus } from "./todo_due_status.ts";  ← from todo.due-status ^1.0.0 · built alongside by fune
import { type Todo } from "./todo_item.ts";  ← from todo.item ^1.0.0 · built alongside by fune

const MONTHS = ["Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec"];

/**
 * The short English label for a todo's due date. Built on dueStatus so the
 * label, the section and the overdue count never disagree. A year is added
 * only when the due date is in a different calendar year from today.
 */
export function dueLabel(todo: Todo, today: string): string {
  const status = dueStatus(todo, today);
  if (status === "done" || status === "none") return "";
  const due = todo.due as string;
  if (status === "overdue") {
    const late = daysBetween(due, today);
    return late === 1 ? "1 day overdue" : `${late} days overdue`;
  }
  if (status === "today") return "Due today";
  if (status === "tomorrow") return "Due tomorrow";
  const d = parseIsoDate(due);
  const label = `Due ${dayName(due).slice(0, 3)} ${d.day} ${MONTHS[d.month - 1]}`;
  return d.year === parseIsoDate(today).year ? label : `${label} ${d.year}`;
}

Install

fune build

With that line in your source, in a TypeScript project (language typescript in fune.project), fune build resolves it and its 5 dependencies, pins them in fune.lock, downloads only the TypeScript package of each, and builds the code above into your project’s .fune/build, one readable file per capability with a header linking back here. Or pin a range in fune.project and build in one step:

fune add todo.due-label

The manifest, vectors and README with only the TypeScript implementation. Install it without the registry with fune add ./todo.due-label-1.0.0-typescript.fune, or fetch it from a terminal with fune pull todo.due-label@1.0.0:typescript.

The whole function, every language, is one file too: todo.due-label-1.0.0.fune, 14,494 bytes, sha256 8aefefe87feab04119b7d82cf60a2bc4f421a0265722e14f34271dd4a0d7e21e. It installs into a project of any language.

// fune: before todo.due-label

// fune: after todo.due-label

// fune: replace dates.add-days in todo.due-label
// fune: replace dates.day-of-week in todo.due-label
// fune: replace dates.days-between in todo.due-label
// fune: replace todo.due-status in todo.due-label
// fune: replace todo.item in todo.due-label

// fune: step todo.due-label after <n|label>

More from the author

- **English only.** Three-letter English weekday and month names, the day without a leading zero. A localised app should not translate these strings: map the `DueStatus` from todo.due-status itself and format the date with its own locale data. - The overdue count is whole calendar days (dates.days-between), since due dates have no time of day. There is no "yesterday": one day late is `"1 day overdue"`. - The year is added whenever the due date is in a different calendar year from today, in either direction, so a date next January is never mistaken for this January. - `today` is passed in by the app. Malformed or impossible dates are errors, with dates.add-days's messages, even on a done todo.

Files