@diagrammo/dgmo 0.47.0 → 0.48.0

package/src/dgmo-router.ts

@@ -1,296 +0,0 @@
-// ============================================================
-// .dgmo Unified Format — Chart Type Router
-// ============================================================
-
-import { looksLikeSequence } from './sequence/parser';
-import { looksLikeFlowchart } from './graph/flowchart-parser';
-import { looksLikeState } from './graph/state-parser';
-import { looksLikeClassDiagram } from './class/parser';
-import { looksLikeERDiagram } from './er/parser';
-import { looksLikeOrg } from './org/parser';
-import { looksLikeSitemap } from './sitemap/parser';
-import { looksLikePert } from './pert/parser';
-// parseVisualization is the no-explicit-type fallback parser in parseDgmo (not
-// part of the derived chartTypeParsers, which come from the registry).
-import { parseVisualization } from './visualizations/parse';
-import { parseFirstLine } from './utils/parsing';
-import { makeDgmoError, suggest, dedupeDiagnostics } from './diagnostics';
-import type { DgmoError } from './diagnostics';
-import { chartTypes } from './chart-types';
-import {
-  CHART_TYPE_REGISTRY,
-  REGISTRY_BY_ID,
-  isExtendedChartParser,
-} from './chart-type-registry';
-import type { RenderCategory } from './chart-type-registry';
-
-// ============================================================
-// Content-based chart type inference helpers
-// ============================================================
-
-/** Gantt duration patterns: `10bd Task` */
-const GANTT_DURATION_RE = /^\d+(?:\.\d+)?(?:min|bd|d|w|m|q|y|h)(?:\?)?\s+/;
-/** Gantt date patterns: `2025-01-01 Task` */
-const GANTT_DATE_RE = /^\d{4}-\d{2}-\d{2}(?:\s\d{2}:\d{2})?\s+/;
-
-/**
- * Returns true if content looks like a gantt chart.
- * Detects duration patterns like `10bd Task` or `5d Task`.
- */
-export function looksLikeGantt(content: string): boolean {
-  const lines = content.split('\n');
-  for (const line of lines) {
-    const trimmed = line.trim();
-    if (!trimmed || trimmed.startsWith('//')) continue;
-    if (GANTT_DURATION_RE.test(trimmed) || GANTT_DATE_RE.test(trimmed)) {
-      return true;
-    }
-  }
-  return false;
-}
-
-/** C4 `Name is a person/system/container/component` pattern */
-const C4_TYPE_RE = /\bis\s+an?\s+(person|system|container|component)\b/i;
-
-/**
- * Returns true if content looks like a C4 diagram.
- * Detects `Name is a person/system/container/component` declarations.
- * Does NOT match bare words like `container` at line start.
- */
-export function looksLikeC4(content: string): boolean {
-  const lines = content.split('\n');
-  for (const line of lines) {
-    const trimmed = line.trim();
-    if (!trimmed || trimmed.startsWith('//')) continue;
-    if (C4_TYPE_RE.test(trimmed)) {
-      return true;
-    }
-  }
-  return false;
-}
-
-/**
- * Extracts the chart type from raw file content.
- * First tries the first non-empty, non-comment line as a bare chart type name
- * (e.g., `gantt Product Launch`).
- * Falls back to inference when no explicit chart type is found.
- */
-export function parseDgmoChartType(content: string): string | null {
-  const lines = content.split('\n');
-
-  // Find first non-empty, non-comment line
-  for (const line of lines) {
-    const trimmed = line.trim();
-    if (!trimmed || trimmed.startsWith('//')) continue;
-
-    // Try new first-line detection (bare chart type name)
-    const firstLineResult = parseFirstLine(trimmed);
-    if (firstLineResult) return firstLineResult.chartType;
-
-    // Not a chart type on the first line — stop looking for explicit declaration
-    break;
-  }
-
-  // Infer chart type from content patterns (sequence before flowchart —
-  // both use `->` but sequence uses bare names while flowchart uses shape delimiters)
-  // C4 must come AFTER sequence (both use `is a` but with different type nouns)
-  if (looksLikeSequence(content)) return 'sequence';
-  if (looksLikeFlowchart(content)) return 'flowchart';
-  if (looksLikeClassDiagram(content)) return 'class';
-  if (looksLikeERDiagram(content)) return 'er';
-  if (looksLikeState(content)) return 'state';
-  if (looksLikeSitemap(content)) return 'sitemap';
-  if (looksLikeOrg(content)) return 'org';
-  if (looksLikeC4(content)) return 'c4';
-  if (looksLikeGantt(content)) return 'gantt';
-  if (looksLikePert(content)) return 'pert';
-
-  return null;
-}
-
-// ============================================================
-// Public render-category API — derived from the chart-type registry.
-// ============================================================
-
-/** User-visible rendering category for dispatch and routing. */
-export type { RenderCategory };
-
-/**
- * Returns the render category for a given chart type, or `null` if unknown.
- * Use this instead of the internal framework map for dispatch in consumers.
- */
-export function getRenderCategory(chartType: string): RenderCategory | null {
-  return REGISTRY_BY_ID.get(chartType.toLowerCase())?.category ?? null;
-}
-
-/**
- * Returns true if the chart type is an extended chart type
- * handled by parseExtendedChart (scatter, sankey, function, heatmap, funnel).
- * Returns false for standard chart types and all other types.
- */
-export function isExtendedChartType(chartType: string): boolean {
-  const descriptor = REGISTRY_BY_ID.get(chartType.toLowerCase());
-  return descriptor ? isExtendedChartParser(descriptor.parse) : false;
-}
-
-/**
- * Returns all supported chart type identifiers in canonical (tier) order,
- * derived from `chartTypes`. Consumers that need alphabetical order should
- * call `.sort()` explicitly.
- */
-export function getAllChartTypes(): string[] {
-  return chartTypes.map((c) => c.id);
-}
-
-/**
- * Canonical descriptions for every supported chart type. Derived from
- * `chartTypes` so there is exactly one place to update when adding a new
- * type. Consumed by the CLI `dgmo types` command, the editor autocomplete
- * popup, and the MCP `list_chart_types` tool.
- */
-export const CHART_TYPE_DESCRIPTIONS: Record<string, string> =
-  Object.fromEntries(chartTypes.map((c) => [c.id, c.description]));
-
-// ============================================================
-// Parser registry — single source of truth for id → parser
-// ============================================================
-
-type ParseResult = { diagnostics: readonly DgmoError[] };
-type ParseFn = (content: string) => ParseResult;
-
-/**
- * Maps every chart-type id to the parser that handles it, DERIVED from
- * `CHART_TYPE_REGISTRY` (src/chart-type-registry.ts). Adding a new chart type
- * means adding ONE descriptor there plus its `chartTypes` metadata entry; the
- * `chart-type-registry.test.ts` cross-check asserts the registry, `chartTypes`,
- * the render-category sites, and the export handlers all stay in sync.
- */
-export const chartTypeParsers: ReadonlyArray<readonly [string, ParseFn]> =
-  CHART_TYPE_REGISTRY.map((d) => [d.id, d.parse] as const);
-
-/** Ids in the same order as `chartTypeParsers`; used for cross-checks. */
-export const knownChartTypeIds: readonly string[] = chartTypeParsers.map(
-  ([id]) => id
-);
-
-const PARSER_BY_ID: Map<string, ParseFn> = new Map(chartTypeParsers);
-
-/** All known chart type names for colon-pattern detection. */
-const ALL_KNOWN_TYPES: ReadonlySet<string> = new Set(knownChartTypeIds);
-
-/**
- * Parse DGMO content and return diagnostics without rendering.
- * Useful for the CLI and editor to surface all errors before attempting render.
- */
-export function parseDgmo(content: string): {
-  diagnostics: DgmoError[];
-  chartType: string | null;
-} {
-  // Dedupe at the parse boundary so one offending line never reports the same
-  // problem N times — keeps the fix-loop signal clean for the CLI, the editor,
-  // and the MCP `validate_diagram` tool.
-  const result = parseDgmoUndeduped(content);
-  return {
-    diagnostics: dedupeDiagnostics(result.diagnostics),
-    chartType: result.chartType,
-  };
-}
-
-function parseDgmoUndeduped(content: string): {
-  diagnostics: DgmoError[];
-  chartType: string | null;
-} {
-  const chartType = parseDgmoChartType(content);
-
-  if (!chartType) {
-    // Check for common mistake: colon in chart type declaration (e.g. "bar: Sales")
-    const colonDiag = detectColonChartType(content);
-    if (colonDiag) {
-      const fallback = parseVisualization(content).diagnostics;
-      return { diagnostics: [colonDiag, ...fallback], chartType: null };
-    }
-
-    // No chart type detected — try visualization parser as fallback
-    return {
-      diagnostics: parseVisualization(content).diagnostics,
-      chartType: null,
-    };
-  }
-
-  const parser = PARSER_BY_ID.get(chartType);
-  if (parser) {
-    const result = parser(content);
-    return {
-      diagnostics: [...result.diagnostics, ...detectEmptyContent(content)],
-      chartType,
-    };
-  }
-
-  // Unknown id (defensive): fall through to visualization parser.
-  const result = parseVisualization(content);
-  return {
-    diagnostics: [...result.diagnostics, ...detectEmptyContent(content)],
-    chartType,
-  };
-}
-
-// ============================================================
-// Common-mistake detectors
-// ============================================================
-
-/**
- * Detects colon-separated chart type declarations like "bar: Sales" or "pie: Data".
- * Returns a diagnostic if the word before the colon is a known or similar chart type.
- */
-function detectColonChartType(content: string): DgmoError | null {
-  const lines = content.split('\n');
-  for (let i = 0; i < lines.length; i++) {
-    // In-bounds by loop guard.
-    const trimmed = lines[i]!.trim();
-    if (!trimmed || trimmed.startsWith('#') || trimmed.startsWith('//'))
-      continue;
-
-    const match = trimmed.match(/^(\w[\w-]*)\s*:\s*(.*)$/);
-    if (!match) return null; // First non-empty line doesn't match colon pattern
-
-    // Regex captured groups 1 and 2 by successful match.
-    const word = match[1]!.toLowerCase();
-    const rest = match[2]!.trim();
-
-    if (ALL_KNOWN_TYPES.has(word)) {
-      const example = rest ? `${word} ${rest}` : word;
-      return makeDgmoError(
-        i + 1,
-        `Remove the colon — use '${example}' instead of '${trimmed}'. DGMO chart types don't use colons.`
-      );
-    }
-
-    // Check if it's a misspelling of a known type
-    const hint = suggest(word, [...ALL_KNOWN_TYPES]);
-    if (hint) {
-      return makeDgmoError(
-        i + 1,
-        `Unknown chart type: ${word}. ${hint} Also, DGMO chart types don't use colons.`
-      );
-    }
-
-    return null; // First line has colon but isn't a chart type — normal data
-  }
-  return null;
-}
-
-/**
- * Detects when content has only the chart type line with no meaningful data lines.
- */
-function detectEmptyContent(content: string): DgmoError[] {
-  const lines = content.split('\n');
-  const nonEmpty = lines.filter(
-    (l) => l.trim() && !l.trim().startsWith('#') && !l.trim().startsWith('//')
-  );
-  if (nonEmpty.length <= 1) {
-    return [
-      makeDgmoError(1, 'No content after chart type declaration.', 'warning'),
-    ];
-  }
-  return [];
-}

package/src/diagnostics-registry.ts

@@ -1,108 +0,0 @@
-// ============================================================
-// Diagnostic Registry — the single enumerable catalog
-// ============================================================
-//
-// Every coded diagnostic dgmo can emit is declared as a `DiagnosticSpec`
-// (see `diagnostics.ts`). This module aggregates the per-chart spec
-// arrays plus the universal (chart-agnostic) codes into one flat list.
-//
-// `listDiagnosticCodes()` is the public entry point every consumer uses
-// to enumerate the catalog: the CLI `diagnostics` subcommand, the
-// console error-review surface, MCP `validate_diagram`, and the spec
-// docs. Keeping one source of truth is what keeps parser output and the
-// language spec's error catalog from drifting.
-//
-// A completeness test (`tests/diagnostics-registry.test.ts`) asserts
-// that every `E_`/`W_`/`I_` code literal in `src/**` appears here with a
-// severity matching its prefix — so a new code can't be added without
-// being cataloged.
-
-import type { DiagnosticSpec } from './diagnostics';
-import { nameMergedMessage, emptyMetadataValueMessage } from './diagnostics';
-import { SWIMLANE_DIAGNOSTICS } from './swimlane/diagnostics';
-import { RACI_DIAGNOSTICS } from './raci/diagnostics';
-import { TREEMAP_DIAGNOSTICS } from './treemap/diagnostics';
-import { EVENT_LINE_DIAGNOSTICS } from './event-line/diagnostics';
-import { VERSION_CONTROL_DIAGNOSTICS } from './version-control/diagnostics';
-import { ARROW_DIAGNOSTICS } from './utils/arrows-diagnostics';
-import { MAP_DIAGNOSTICS } from './map/diagnostics';
-import { PERT_DIAGNOSTICS } from './pert/diagnostics';
-import { GRAPH_DIAGNOSTICS } from './graph/diagnostics';
-import { COLOR_DIAGNOSTICS } from './colors-diagnostics';
-
-// ── Universal codes (chartType: null) ───────────────────────
-// Name handling, alias syntax, and metadata grammar apply to every
-// chart type, so they carry no owning chart. Canonical wording comes
-// from the message builders in `diagnostics.ts` where they exist.
-
-export const UNIVERSAL_DIAGNOSTICS: DiagnosticSpec[] = [
-  // ── Universal name handling ──
-  {
-    code: 'I_NAME_MERGED',
-    severity: 'warning',
-    chartType: null,
-    title: 'Names merged (case/whitespace)',
-    message: (p) =>
-      nameMergedMessage({
-        incomingDisplay: String(p.incomingDisplay ?? 'Backend'),
-        incomingLine: Number(p.incomingLine ?? 2),
-        existingDisplay: String(p.existingDisplay ?? 'backend'),
-        existingLine: Number(p.existingLine ?? 1),
-      }),
-    hint: 'Use one consistent spelling, or add `# allow-merge` on the line if the merge is intentional.',
-    example: 'infra\ninternet\n  -> gw\ngw\n  -> svc\nGW\n  -> svc\n',
-  },
-
-  // ── Unified metadata grammar (0.18.0) ──
-  {
-    code: 'E_TAG_DECLARED_AFTER_CONTENT',
-    severity: 'error',
-    chartType: null,
-    title: 'Tag declared after content',
-    message:
-      'A `tag` declaration appears after the first content line — declare all tags before any content.',
-    hint: 'Move `tag` declarations to the top of the diagram.',
-    example: 'block\n[A]\ntag warn red',
-  },
-  {
-    code: 'W_EMPTY_METADATA_VALUE',
-    severity: 'warning',
-    chartType: null,
-    title: 'Empty metadata value',
-    message: (p) => emptyMetadataValueMessage(String(p.key ?? 'color')),
-    hint: 'Provide a value or remove the key.',
-    example: 'mindmap\nRoot color:\n  Child',
-  },
-];
-
-// ── Aggregate ───────────────────────────────────────────────
-
-const REGISTRY: DiagnosticSpec[] = [
-  ...UNIVERSAL_DIAGNOSTICS,
-  ...SWIMLANE_DIAGNOSTICS,
-  ...RACI_DIAGNOSTICS,
-  ...TREEMAP_DIAGNOSTICS,
-  ...EVENT_LINE_DIAGNOSTICS,
-  ...VERSION_CONTROL_DIAGNOSTICS,
-  ...ARROW_DIAGNOSTICS,
-  ...MAP_DIAGNOSTICS,
-  ...PERT_DIAGNOSTICS,
-  ...GRAPH_DIAGNOSTICS,
-  ...COLOR_DIAGNOSTICS,
-];
-
-/**
- * The full diagnostic catalog, sorted by code. Every coded diagnostic
- * dgmo can emit — its severity, owning chart type, canonical message,
- * fix hint, and a triggering example. This is the enumerable source of
- * truth for the CLI `diagnostics` subcommand, the console error-review
- * surface, MCP, and the language-spec catalog.
- */
-export function listDiagnosticCodes(): DiagnosticSpec[] {
-  return [...REGISTRY].sort((a, b) => a.code.localeCompare(b.code));
-}
-
-/** Look up a single spec by its code, or `undefined` if not cataloged. */
-export function getDiagnosticSpec(code: string): DiagnosticSpec | undefined {
-  return REGISTRY.find((s) => s.code === code);
-}

package/src/dimensions.ts

@@ -1,20 +0,0 @@
-import { parseDgmo } from './dgmo-router';
-import type { ContentCounts } from './utils/scaling';
-import { REGISTRY_BY_ID } from './chart-type-registry';
-
-export function getMinDimensions(content: string): {
-  width: number;
-  height: number;
-} {
-  const { chartType } = parseDgmo(content);
-  if (!chartType) return { width: 300, height: 200 };
-
-  // Both halves of sizing are owned by the chart type's descriptor in
-  // chart-type-registry.ts: `measure` (content → counts) and `minDims`
-  // (counts → min size). One lookup serves both. Types without a `minDims`
-  // fall back to {300,200} — the previous silent `default:` arm of
-  // computeMinDimensions; `measure`-less types contribute `{}` counts.
-  const descriptor = REGISTRY_BY_ID.get(chartType);
-  const counts: ContentCounts = descriptor?.measure?.(content) ?? {};
-  return descriptor?.minDims?.(counts) ?? { width: 300, height: 200 };
-}