@hachej/boring-tasks 0.1.79

package/README.md

@@ -0,0 +1,27 @@
+# @hachej/boring-tasks
+
+Lean Kanban task-board plugin for boring-ui.
+
+`boring-tasks` owns only the generic board UI:
+
+- standard task cards: number, title, description;
+- adapter selector;
+- flexible adapter-supplied columns;
+- drag/drop status moves;
+- optimistic update and revert.
+
+Source-specific behavior belongs in adapters. A GitHub, Linear, Kata, or custom DB adapter maps native status/actions to the normalized board model; the Kanban UI does not know those systems.
+
+The server plugin reads its own plugin config and creates task sources from it. In CLI workspaces mode, the host stores this config under the workspace's opaque `plugins.tasks` section:
+
+```yaml
+plugins:
+  tasks:
+    providers:
+      - provider: github
+        repo: auto
+      - provider: github
+        repo: hachej/boring-ui
+```
+
+`repo: auto` detects the repository with `gh repo view --json nameWithOwner` from the workspace root, so each local CLI workspace can map to its own associated GitHub repo. The GitHub source requires `gh auth login` and repository access. If no Tasks config is present, the backend exposes no task sources. If backend routes are unavailable, the front end still falls back to demo adapters for review/playground usage.

package/dist/front/index.d.ts

@@ -0,0 +1,42 @@
+import { BoringFrontAppLeftOverlayProps, BoringFrontFactoryWithId } from '@hachej/boring-workspace/plugin';
+import * as react from 'react';
+import { BoringTaskAdapter, BoringTaskCard, BoringTaskAdapterSummary } from '../shared/index.js';
+export { BoringTaskAdapterCapabilities, BoringTaskBoardConfig, BoringTaskColumn, BoringTaskEpicRef, BoringTaskMoveInput, BoringTaskStatusId } from '../shared/index.js';
+import { WorkspacePluginClient } from '@hachej/boring-workspace';
+
+interface TaskKanbanBoardProps {
+    adapters: readonly BoringTaskAdapter[];
+}
+declare function TaskKanbanBoard({ adapters }: TaskKanbanBoardProps): react.JSX.Element;
+
+declare function TasksOverlay({ onClose }: BoringFrontAppLeftOverlayProps): react.JSX.Element;
+
+interface GitHubMoveIssueInput {
+    owner: string;
+    repo: string;
+    issueNumber: number;
+    statusId: string;
+}
+interface GitHubIssuesAdapterOptions {
+    owner: string;
+    repo: string;
+    limit?: number;
+    state?: "open" | "closed" | "all";
+    /**
+     * Optional hosted mover. The browser demo intentionally omits this; hosted
+     * apps can route it to a backend that uses `gh` CLI today or GitHub API later.
+     */
+    moveIssue?: (input: GitHubMoveIssueInput) => Promise<BoringTaskCard | void> | BoringTaskCard | void;
+}
+declare function createGitHubIssuesAdapter({ owner, repo, limit, state, moveIssue }: GitHubIssuesAdapterOptions): BoringTaskAdapter;
+
+type TaskHttpClient = Pick<WorkspacePluginClient, "getJson" | "postJson">;
+declare function listHttpTaskSources(client?: TaskHttpClient): Promise<BoringTaskAdapterSummary[]>;
+declare function createHttpTaskAdapter(source: BoringTaskAdapterSummary, client?: TaskHttpClient): BoringTaskAdapter;
+
+declare function createMockTaskAdapter(initialTasks?: readonly BoringTaskCard[]): BoringTaskAdapter;
+
+declare function createTasksPlugin(): BoringFrontFactoryWithId;
+declare const tasksPlugin: BoringFrontFactoryWithId;
+
+export { BoringTaskAdapter, BoringTaskAdapterSummary, BoringTaskCard, TaskKanbanBoard, TasksOverlay, createGitHubIssuesAdapter, createHttpTaskAdapter, createMockTaskAdapter, createTasksPlugin, tasksPlugin as default, listHttpTaskSources };