Skip to content

refactor: use git-warp API properly — eliminate pass-through wrappers #295

@flyingrobots

Description

@flyingrobots

Summary

git-mind wraps @git-stunts/git-warp in thin abstraction layers that obscure the real API and duplicate capabilities the graph engine already provides. This issue tracks eliminating unnecessary wrappers and replacing hand-rolled logic with native WARP APIs.

Phases

  • Phase 1: Kill pass-through wrappers (getNodes, hasNode, saveGraph, loadGraph)
  • Phase 2: Replace thin wrappers with native API (getNodesByPrefix, queryEdges, getNode)
  • Phase 3: Use query API in views
  • Phase 4: Use graph.patch() convenience API
  • Phase 5: Content — verify native API alignment
  • Phase 6: Evaluate dag.js vs graph.traverse

Motivation

  • Reduce indirection and make the codebase speak git-warp fluently
  • Remove dead code (saveGraph has zero call sites)
  • Eliminate ~60 call site updates of wrapper functions that add zero value

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions