@telorun/ide-support 0.4.44 → 0.5.0

package/dist/diagnostics/graph-diagnostics.d.ts

@@ -0,0 +1,44 @@
+import { type AnalysisDiagnostic, type LoadedGraph } from "@telorun/analyzer";
+/**
+ * Files whose static-analysis output is an unreliable cascade rather than a set
+ * of independent defects:
+ *
+ * - a file that **failed to parse** yields a mangled `toJSON()` tree, so its
+ *   analyze-derived diagnostics are spurious;
+ * - a file whose **import failed to resolve** has broken kind resolution, so it
+ *   emits a wall of secondary `UNDEFINED_KIND` etc. for every use of the missing
+ *   alias.
+ *
+ * Both surface a coded parse / import diagnostic of their own (kept, always);
+ * their *analysis* diagnostics are what a host suppresses so the real cause is
+ * not buried. Every host computes this set from the one function, so the CLI,
+ * VS Code, and telo-editor agree on exactly what is compromised.
+ */
+export declare function compromisedFiles(graph: LoadedGraph): Set<string>;
+/**
+ * Assemble the complete diagnostic set for a loaded graph and partition it into
+ * what to surface (`diagnostics`) and the compromised-file cascade held back
+ * (`suppressed`). The presentation policy lives here — not in the analyzer,
+ * which only emits raw channels — so every host applies it identically.
+ *
+ * `diagnostics` folds parse, version-reconciliation, import-resolution, and the
+ * *live* analysis diagnostics (those on non-compromised files) into one list,
+ * in that order. `suppressed` carries the analysis cascade dropped from
+ * compromised files, still available to a host that wants to render it dimmed /
+ * as related information rather than hide it.
+ *
+ * A diagnostic's owning file is resolved via {@link findPositions} (resource
+ * identity first), falling back to the raw `data.filePath` — which
+ * `findPositions` cannot resolve for a file absent from `graph.modules` (e.g. a
+ * parse-failed file) — then the entry source.
+ *
+ * Single-closure hosts (CLI, VS Code) call this directly. The multi-closure
+ * telo-editor drives analysis per closure with bespoke routing, so it consumes
+ * {@link compromisedFiles} and {@link importResolutionDiagnostics} on their own
+ * — but through the same shared policy, never a private reimplementation.
+ */
+export declare function assembleGraphDiagnostics(graph: LoadedGraph, analysisDiagnostics: AnalysisDiagnostic[]): {
+    diagnostics: AnalysisDiagnostic[];
+    suppressed: AnalysisDiagnostic[];
+};
+//# sourceMappingURL=graph-diagnostics.d.ts.map

package/dist/diagnostics/graph-diagnostics.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"graph-diagnostics.d.ts","sourceRoot":"","sources":["../../src/diagnostics/graph-diagnostics.ts"],"names":[],"mappings":"AAAA,OAAO,EAEL,KAAK,kBAAkB,EACvB,KAAK,WAAW,EACjB,MAAM,mBAAmB,CAAC;AAG3B;;;;;;;;;;;;;;GAcG;AACH,wBAAgB,gBAAgB,CAAC,KAAK,EAAE,WAAW,GAAG,GAAG,CAAC,MAAM,CAAC,CAShE;AAED;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,wBAAgB,wBAAwB,CACtC,KAAK,EAAE,WAAW,EAClB,mBAAmB,EAAE,kBAAkB,EAAE,GACxC;IAAE,WAAW,EAAE,kBAAkB,EAAE,CAAC;IAAC,UAAU,EAAE,kBAAkB,EAAE,CAAA;CAAE,CAoBzE"}

package/dist/diagnostics/graph-diagnostics.js

@@ -0,0 +1,71 @@
+import { importResolutionDiagnostics, } from "@telorun/analyzer";
+import { findPositions } from "./find-positions.js";
+/**
+ * Files whose static-analysis output is an unreliable cascade rather than a set
+ * of independent defects:
+ *
+ * - a file that **failed to parse** yields a mangled `toJSON()` tree, so its
+ *   analyze-derived diagnostics are spurious;
+ * - a file whose **import failed to resolve** has broken kind resolution, so it
+ *   emits a wall of secondary `UNDEFINED_KIND` etc. for every use of the missing
+ *   alias.
+ *
+ * Both surface a coded parse / import diagnostic of their own (kept, always);
+ * their *analysis* diagnostics are what a host suppresses so the real cause is
+ * not buried. Every host computes this set from the one function, so the CLI,
+ * VS Code, and telo-editor agree on exactly what is compromised.
+ */
+export function compromisedFiles(graph) {
+    const entrySource = graph.entry.owner.source;
+    const files = new Set();
+    for (const d of graph.parseDiagnostics) {
+        const f = d.data?.filePath;
+        if (f)
+            files.add(f);
+    }
+    for (const e of graph.errors)
+        files.add(e.fromSource ?? entrySource);
+    return files;
+}
+/**
+ * Assemble the complete diagnostic set for a loaded graph and partition it into
+ * what to surface (`diagnostics`) and the compromised-file cascade held back
+ * (`suppressed`). The presentation policy lives here — not in the analyzer,
+ * which only emits raw channels — so every host applies it identically.
+ *
+ * `diagnostics` folds parse, version-reconciliation, import-resolution, and the
+ * *live* analysis diagnostics (those on non-compromised files) into one list,
+ * in that order. `suppressed` carries the analysis cascade dropped from
+ * compromised files, still available to a host that wants to render it dimmed /
+ * as related information rather than hide it.
+ *
+ * A diagnostic's owning file is resolved via {@link findPositions} (resource
+ * identity first), falling back to the raw `data.filePath` — which
+ * `findPositions` cannot resolve for a file absent from `graph.modules` (e.g. a
+ * parse-failed file) — then the entry source.
+ *
+ * Single-closure hosts (CLI, VS Code) call this directly. The multi-closure
+ * telo-editor drives analysis per closure with bespoke routing, so it consumes
+ * {@link compromisedFiles} and {@link importResolutionDiagnostics} on their own
+ * — but through the same shared policy, never a private reimplementation.
+ */
+export function assembleGraphDiagnostics(graph, analysisDiagnostics) {
+    const compromised = compromisedFiles(graph);
+    const entrySource = graph.entry.owner.source;
+    const live = [];
+    const suppressed = [];
+    for (const d of analysisDiagnostics) {
+        const rawFilePath = d.data?.filePath;
+        const file = findPositions(graph, d.data)?.file ?? rawFilePath ?? entrySource;
+        (compromised.has(file) ? suppressed : live).push(d);
+    }
+    return {
+        diagnostics: [
+            ...graph.parseDiagnostics,
+            ...graph.versionDiagnostics,
+            ...importResolutionDiagnostics(graph),
+            ...live,
+        ],
+        suppressed,
+    };
+}

package/dist/diagnostics/index.d.ts

@@ -1,4 +1,5 @@
 export { findPositions } from "./find-positions.js";
+export { assembleGraphDiagnostics, compromisedFiles } from "./graph-diagnostics.js";
 export { normalizeDiagnostic } from "./normalize.js";
 export { resolveRange } from "./range-resolver.js";
 export { resolveSeverity } from "./severity.js";

package/dist/diagnostics/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/diagnostics/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,MAAM,qBAAqB,CAAC;AACpD,OAAO,EAAE,mBAAmB,EAAE,MAAM,gBAAgB,CAAC;AACrD,OAAO,EAAE,YAAY,EAAE,MAAM,qBAAqB,CAAC;AACnD,OAAO,EAAE,eAAe,EAAE,MAAM,eAAe,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/diagnostics/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,MAAM,qBAAqB,CAAC;AACpD,OAAO,EAAE,wBAAwB,EAAE,gBAAgB,EAAE,MAAM,wBAAwB,CAAC;AACpF,OAAO,EAAE,mBAAmB,EAAE,MAAM,gBAAgB,CAAC;AACrD,OAAO,EAAE,YAAY,EAAE,MAAM,qBAAqB,CAAC;AACnD,OAAO,EAAE,eAAe,EAAE,MAAM,eAAe,CAAC"}

package/dist/diagnostics/index.js

@@ -1,4 +1,5 @@
 export { findPositions } from "./find-positions.js";
+export { assembleGraphDiagnostics, compromisedFiles } from "./graph-diagnostics.js";
 export { normalizeDiagnostic } from "./normalize.js";
 export { resolveRange } from "./range-resolver.js";
 export { resolveSeverity } from "./severity.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@telorun/ide-support",
-  "version": "0.4.44",
+  "version": "0.5.0",
   "description": "Editor-host-agnostic IDE support (completions, diagnostic normalization) for Telo manifests.",
   "keywords": [
     "telo",
@@ -36,7 +36,7 @@
     "src/**"
   ],
   "dependencies": {
-    "@telorun/analyzer": "0.38.0"
+    "@telorun/analyzer": "0.40.0"
   },
   "devDependencies": {
     "@types/node": "^20.0.0",

package/src/diagnostics/graph-diagnostics.ts

@@ -0,0 +1,79 @@
+import {
+  importResolutionDiagnostics,
+  type AnalysisDiagnostic,
+  type LoadedGraph,
+} from "@telorun/analyzer";
+import { findPositions } from "./find-positions.js";
+
+/**
+ * Files whose static-analysis output is an unreliable cascade rather than a set
+ * of independent defects:
+ *
+ * - a file that **failed to parse** yields a mangled `toJSON()` tree, so its
+ *   analyze-derived diagnostics are spurious;
+ * - a file whose **import failed to resolve** has broken kind resolution, so it
+ *   emits a wall of secondary `UNDEFINED_KIND` etc. for every use of the missing
+ *   alias.
+ *
+ * Both surface a coded parse / import diagnostic of their own (kept, always);
+ * their *analysis* diagnostics are what a host suppresses so the real cause is
+ * not buried. Every host computes this set from the one function, so the CLI,
+ * VS Code, and telo-editor agree on exactly what is compromised.
+ */
+export function compromisedFiles(graph: LoadedGraph): Set<string> {
+  const entrySource = graph.entry.owner.source;
+  const files = new Set<string>();
+  for (const d of graph.parseDiagnostics) {
+    const f = (d.data as { filePath?: string } | undefined)?.filePath;
+    if (f) files.add(f);
+  }
+  for (const e of graph.errors) files.add(e.fromSource ?? entrySource);
+  return files;
+}
+
+/**
+ * Assemble the complete diagnostic set for a loaded graph and partition it into
+ * what to surface (`diagnostics`) and the compromised-file cascade held back
+ * (`suppressed`). The presentation policy lives here — not in the analyzer,
+ * which only emits raw channels — so every host applies it identically.
+ *
+ * `diagnostics` folds parse, version-reconciliation, import-resolution, and the
+ * *live* analysis diagnostics (those on non-compromised files) into one list,
+ * in that order. `suppressed` carries the analysis cascade dropped from
+ * compromised files, still available to a host that wants to render it dimmed /
+ * as related information rather than hide it.
+ *
+ * A diagnostic's owning file is resolved via {@link findPositions} (resource
+ * identity first), falling back to the raw `data.filePath` — which
+ * `findPositions` cannot resolve for a file absent from `graph.modules` (e.g. a
+ * parse-failed file) — then the entry source.
+ *
+ * Single-closure hosts (CLI, VS Code) call this directly. The multi-closure
+ * telo-editor drives analysis per closure with bespoke routing, so it consumes
+ * {@link compromisedFiles} and {@link importResolutionDiagnostics} on their own
+ * — but through the same shared policy, never a private reimplementation.
+ */
+export function assembleGraphDiagnostics(
+  graph: LoadedGraph,
+  analysisDiagnostics: AnalysisDiagnostic[],
+): { diagnostics: AnalysisDiagnostic[]; suppressed: AnalysisDiagnostic[] } {
+  const compromised = compromisedFiles(graph);
+  const entrySource = graph.entry.owner.source;
+  const live: AnalysisDiagnostic[] = [];
+  const suppressed: AnalysisDiagnostic[] = [];
+  for (const d of analysisDiagnostics) {
+    const rawFilePath = (d.data as { filePath?: string } | undefined)?.filePath;
+    const file = findPositions(graph, d.data)?.file ?? rawFilePath ?? entrySource;
+    (compromised.has(file) ? suppressed : live).push(d);
+  }
+
+  return {
+    diagnostics: [
+      ...graph.parseDiagnostics,
+      ...graph.versionDiagnostics,
+      ...importResolutionDiagnostics(graph),
+      ...live,
+    ],
+    suppressed,
+  };
+}

package/src/diagnostics/index.ts

@@ -1,4 +1,5 @@
 export { findPositions } from "./find-positions.js";
+export { assembleGraphDiagnostics, compromisedFiles } from "./graph-diagnostics.js";
 export { normalizeDiagnostic } from "./normalize.js";
 export { resolveRange } from "./range-resolver.js";
 export { resolveSeverity } from "./severity.js";