C
ConvexCompose
Modules
← All modules
T

Tasks

Component in production Project Mgmt

Issues, projects, and bug reports, composed

app.use(tasks) Future install shape; not yet published

About

Polymorphic issues (task / bug / feature / equipment / support) with inline list editing, projects, sprints, and entity linking by explicit ID. It now runs as an authored Convex Component in production, with data migrated and the old root tables dropped; headless hooks and packaging are pending.

How it ships

Every ConvexCompose module is the same shape. Take the Component and hooks and bring your own UI, or drop in the optional reference UI.

Layer 1 · MUST
A Convex Component (convex.config.ts + schema + functions), app.use()-installable into your deployment
Layer 2 · MUST
Headless useX() hooks: router-free, style-free, navigation passed in as callbacks
Layer 3 · OPTIONAL
An OPTIONAL React Native + NativeWind reference UI; ignore it and bring your own surface

Highlights

  • Authored Component live in production
  • Headless hooks and packaging pending
  • Polymorphic issues with type discriminator
  • Inline list editing
  • Cross-module entity linking by explicit ID

Proving ground

A real production deployment exercises these domains; one opinionated consumer, not a requirement.

T
A real production deployment
50+ portals on one Convex deployment

Not a published package yet

No ConvexCompose module is an installable npm package today. What exists is the contract, a real production proving ground running 31 authored Components, and packaging in progress led by convex-diary and convex-audio-analyzer.