8000 Reaching the queue from the prose · Issue #39 · kiran-brahma/writing-tool · GitHub
[go: up one dir, main page]

Skip to content

Reaching the queue from the prose #39

Closed

Description

@kiran-brahma

Parent

#34 — the Obelus v1.2 spec (docs/specs/obelus-v1.2.md). Covers stories 176–178.

Blocked by #35 — the rail restructures FindingsSidebar, which owns the hint bar.

What to build

The hint bar advertises j / k / a / x / v unconditionally. The handler in src/App.tsx
correctly stands those keys down while a field or the Editor has focus — they are ordinary letters
and must reach the prose — so the keys it advertises do nothing where the Writer actually is, and the
only way into the queue is to click a Finding.

Three parts:

  1. Leave the plain keys exactly as they are, guard included. Do not make them fire while typing.
  2. Add a modifier shortcut that steps the queue from inside the Editor and moves the selection
    into it, so working Findings does not require the mouse. It must not collide with a browser or
    OS binding, or with TipTap's own bindings.
  3. Tell the truth in the hint bar: state the condition under which the plain keys are live, and
    name the modifier shortcut that works anywhere.

? opens the shortcuts section of How this works (#36).

Where

  • src/App.tsx — the keydown effect; isTypingTarget stays as the guard for the plain keys.
  • src/editor/FindingsSidebar.tsx — the hint bar copy.
  • src/help/helpContent.ts — the shortcut list, which must match what the app binds.

Acceptance criteria

  • A modifier shortcut steps the queue while the cursor is in the prose, and moves the selection
    into the queue. (story 176)
  • The plain j/k/a/x/v keys are unchanged, still stand down inside the Editor and any
    field, and still belong to the Findings view only. (story 176)
  • The hint bar states when the plain keys are live instead of advertising them unconditionally.
    (story 177)
  • ? opens the shortcuts. (story 178)
  • The shortcut list in How this works matches the keys the app actually binds.
  • No new shortcut shadows a browser, OS or TipTap binding.

Verification

A pure test over the key-dispatch decision — given a key, modifiers and a target kind, which queue
action results — so the guard is covered without a DOM.

No DOM layer. State the observable checks you ran from inside the Editor.

Constitution

Unchanged. No shortcut addresses, accepts or inserts model-derived text; a and x write a Finding
status and nothing else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentSpec is ready for an agent to implement

    Projects

    No projects
      3738

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0