Remove or wire up dead controls: header search box and video row "more" button

Open
  • Is something wrong?
#33 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
66/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
bash, nextjs, playwright, typescript
Domain
accessibility, frontend

Research direction

Start with frontend/src/components/shell/AppShell.tsx and frontend/src/app/videos/page.tsx to review the two inert controls and the existing store API in frontend/src/stores/video-store.ts. Implement a real outcome for each, using frontend/src/lib/local-db.ts if search is retained, and add the corresponding Playwright coverage. Done means every retained control works and is keyboard accessible, the verification script and lint/build pass, and screenshots are attached.

Written by the indexing model from the issue text.

Description

help wanted ui
Context

Law L1 (zero facades) says every control must lead to a real result. Two controls currently do nothing. The global header search input has no value, onChange or submit handler, yet it shows a ⌘K hint that is never bound. The "more" (MoreHorizontal) button on each row of the Videos list has no onClick and no accessible name. Both look interactive and do nothing.

Where
  • frontend/src/components/shell/AppShell.tsx:328-342: search <input> and ⌘K <kbd>
  • frontend/src/app/videos/page.tsx:300-305: <button> with <MoreHorizontal/>, no handler
What to do

Pick a real outcome for each control and describe it in the PR:

  1. Search: implement client-side search over the app's routes/tools plus local projects (IndexedDB via src/lib/local-db.ts, with no backend required, per L2), and bind ⌘K/Ctrl+K to focus it. Or remove the input and the hint entirely.
  2. Row menu: wire it to actions the store already supports (deleteVideo exists at src/stores/video-store.ts:92), with aria-label="More actions for <title>" and keyboard support. Or remove it.
  3. No placeholder menus with disabled "soon" items.
Acceptance criteria
  • Every remaining control produces a real result, covered by a Playwright spec
  • bash scripts/verify.sh --quick passes
  • lint and build pass; screenshots attached
Getting started

Read CONTRIBUTING.md for dev setup and the quality bar (no facades, evidence before done). Comment here to claim the issue.

Dominant language
TypeScript
Stars
0
Forks
3
Avg merge
1d 4h
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from BeyondITL/contentine-create

All issues in BeyondITL/contentine-create

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.