mAi
41c1eaadaa
Big task. Five migrations, full store + web rewrite, and a model upgrade
that turns the parent_id tree into a parent_ids[] DAG.
Schema (db/migrations)
- 0006_tags_management_unify: adds tags + management text[] (GIN-indexed),
collapses the area/project distinction (kind keeps the slot but 'area'
is no longer a special value), drops the structural rules from the
path trigger so root projects + non-root projects are both legal.
- 0007_backfill_mai_projects: one-shot, idempotent — for every row in
mai.projects without a 'mai-project' item_link, create a projax.items
row under a heuristic-chosen area (mhealth→health, msports/manjin→
sports, kanzlai/hlckm/work/mworkrepo/paliad or HL/* repo→work,
mhome→home, default→dev), insert the item_link, and tag the row
management=['mai']. Also flips management='mai' on any already-linked
pre-Phase-1.5 promotions.
- 0008_mai_projects_sync: bidirectional triggers. sync_to_mai runs as
projax_admin and writes mai.projects directly (after the operator-run
grant + RLS policy widening — documented in the migration header).
sync_from_mai is SECURITY DEFINER so writes by the mai role fan out
into projax.items. pg_trigger_depth() + projax.in_sync GUC keep the
cycle suppressed. Slug stays the join key for new rows; the
item_link pointer survives renames.
- 0009_items_unified_simplify: view collapses to a thin projection over
projax.items now that mai.projects is a derived projection.
- 0010_multi_parent: parent_id → parent_ids uuid[], path → paths text[].
compute_item_paths walks via parents' precomputed paths (no recursive
CTE in the hot path; cycle detection uses one). New triggers:
items_check_slug_collision (multi-parent uniqueness),
items_after_delete (manual cascade since arrays don't carry FK).
Trigger refresh_item_paths_recursive does parent-first DFS over
descendants, guarded by projax.refreshing_paths GUC.
Go store + handlers
- Item gains ParentIDs []string + Paths []string. PrimaryPath /
OtherPaths helpers feed the detail breadcrumb. Source always
'projax' now; SourceRefDeref still surfaces the mai-id pointer.
- Update / Reparent / Create take ParentIDs []string. AddParent helper
for the multi-parent UI's "also list under" action.
- GetByPath uses '$1 = any(paths)' so /i/work.paliad and /i/dev.paliad
resolve to the same row.
- buildForest renders a multi-parent item under each of its parents
(duplicated nodes in distinct branches). Tag-filter prune is
branch-preserving.
Templates
- detail.tmpl: multi-select parents, tags + management chip inputs,
"Also at: …" breadcrumb for multi-parent items.
- new.tmpl: same multi-select + chip inputs.
- tree.tmpl: tag-filter chip bar, "×N" badge on multi-parent rows,
management chips visible on every row.
- classify.tmpl: re-parent workflow (no more promote-to-projax — the
bidirectional sync removed the dichotomy).
Tests (DB + HTTP, all skip without env)
- TestMultiParentResolvesBothPaths inserts an item with two parents,
asserts both inherited paths.
- TestSlugCollisionUnderCommonParent refuses a sibling clash.
- TestMultiParentBothPathsRouteToSameRow HTTP-level: /i/dev.X and
/i/work.X both 200, same row.
- TestReparentRoundTrip rewritten for parent_ids[] semantics.
- TestPathTriggerNestAndRename / Reparent rewritten to query paths[].
Docs (docs/design.md)
- §2 rewritten: items in a DAG, no area/project distinction.
- §3 schema: parent_ids + paths + tags + management + indices.
- §3.1 path-trigger overhaul incl. cycle detection via recursive CTE
and slug-collision-under-common-parent guard.
- §3.2 view simplified.
- §3.4 NEW: mai.projects bidirectional sync, including the manual
prereq.
- §4.1 + §4.2: classify becomes re-parent, tags+management UI section.
mai head start / mai hire / mai status / mai instruct keep working
because mai.projects retains its FK-target shape; the projax sync just
mirrors the row in lock-step.
55 lines
2.0 KiB
Cheetah
55 lines
2.0 KiB
Cheetah
{{define "content"}}
|
||
<h1>Tree</h1>
|
||
<p class="counts">
|
||
<strong>{{.Total}}</strong> items
|
||
{{if .OrphanN}} · <strong>{{.OrphanN}}</strong> unclassified mai-managed roots <a href="/admin/classify">→ classify</a>{{end}}
|
||
</p>
|
||
|
||
{{if .AllTags}}
|
||
<section class="tagbar">
|
||
<span class="muted">Filter by tag:</span>
|
||
{{range .AllTags}}
|
||
{{$on := false}}{{range $t := $.ActiveTags}}{{if eq $t .}}{{$on = true}}{{end}}{{end}}
|
||
{{if $on}}<a class="tag tag-on" href="{{tagToggleURL $.ActiveTags . true}}">{{.}}</a>{{else}}<a class="tag" href="{{tagToggleURL $.ActiveTags . false}}">{{.}}</a>{{end}}
|
||
{{end}}
|
||
{{if .ActiveTags}}<a class="clear" href="/">clear</a>{{end}}
|
||
</section>
|
||
{{end}}
|
||
|
||
<section class="tree">
|
||
<ul class="forest">
|
||
{{range .Roots}}
|
||
<li class="node root">
|
||
<a href="/i/{{.Item.PrimaryPath}}">{{.Item.Title}}</a>
|
||
<span class="slug">{{.Item.PrimaryPath}}</span>
|
||
{{range .Item.Management}}<span class="mgmt mgmt-{{.}}">{{.}}</span>{{end}}
|
||
{{range .Item.Tags}}<span class="tag">{{.}}</span>{{end}}
|
||
<a class="add" href="/new?parent={{.Item.PrimaryPath}}">+</a>
|
||
{{template "children" .}}
|
||
</li>
|
||
{{else}}
|
||
<li><em>No items match the active filter.</em></li>
|
||
{{end}}
|
||
</ul>
|
||
</section>
|
||
{{end}}
|
||
|
||
{{define "children"}}
|
||
{{if .Children}}
|
||
<ul>
|
||
{{range .Children}}
|
||
<li class="node project">
|
||
<a href="/i/{{.Item.PrimaryPath}}">{{.Item.Title}}</a>
|
||
<span class="slug">{{.Item.PrimaryPath}}</span>
|
||
<span class="status status-{{.Item.Status}}">{{.Item.Status}}</span>
|
||
{{if gt (len .Item.Paths) 1}}<span class="muted multi-parent" title="appears under multiple parents">×{{len .Item.Paths}}</span>{{end}}
|
||
{{range .Item.Management}}<span class="mgmt mgmt-{{.}}">{{.}}</span>{{end}}
|
||
{{range .Item.Tags}}<span class="tag">{{.}}</span>{{end}}
|
||
<a class="add" href="/new?parent={{.Item.PrimaryPath}}">+</a>
|
||
{{template "children" .}}
|
||
</li>
|
||
{{end}}
|
||
</ul>
|
||
{{end}}
|
||
{{end}}
|