@telorun/ide-support 0.16.1 → 0.17.0

package/dist/completions/index.d.ts

@@ -1,3 +1,5 @@
 export { buildCompletions } from "./build.js";
 export type { CompletionCtx } from "./detect-context.js";
+export { celCompletions } from "./cel-completions.js";
+export type { CelCompletionTarget } from "./cel-completions.js";
 //# sourceMappingURL=index.d.ts.map

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

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/completions/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,gBAAgB,EAAE,MAAM,YAAY,CAAC;AAC9C,YAAY,EAAE,aAAa,EAAE,MAAM,qBAAqB,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/completions/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,gBAAgB,EAAE,MAAM,YAAY,CAAC;AAC9C,YAAY,EAAE,aAAa,EAAE,MAAM,qBAAqB,CAAC;AAKzD,OAAO,EAAE,cAAc,EAAE,MAAM,sBAAsB,CAAC;AACtD,YAAY,EAAE,mBAAmB,EAAE,MAAM,sBAAsB,CAAC"}

package/dist/completions/index.js

@@ -1 +1,6 @@
 export { buildCompletions } from "./build.js";
+// The CEL half on its own, for a host completing an expression that is not in a
+// YAML document: studio's schema form edits a `!cel` body in a field, so it has
+// the site's address directly and nothing to detect a context from.
+// `buildCompletions` stays the entry point for a document plus a cursor.
+export { celCompletions } from "./cel-completions.js";

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

@@ -12,7 +12,7 @@ import { type AnalysisDiagnostic, type LoadedGraph } from "@telorun/analyzer";
  * 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.
+ * VS Code, and telo studio agree on exactly what is compromised.
  */
 export declare function compromisedFiles(graph: LoadedGraph): Set<string>;
 /**
@@ -33,7 +33,7 @@ export declare function compromisedFiles(graph: LoadedGraph): Set<string>;
  * 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
+ * telo studio 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.
  */

package/dist/diagnostics/graph-diagnostics.js

@@ -13,7 +13,7 @@ import { findPositions } from "./find-positions.js";
  * 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.
+ * VS Code, and telo studio agree on exactly what is compromised.
  */
 export function compromisedFiles(graph) {
     const entrySource = graph.entry.owner.source;
@@ -45,7 +45,7 @@ export function compromisedFiles(graph) {
  * 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
+ * telo studio 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.
  */

package/package.json

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

package/src/completions/index.ts

@@ -1,2 +1,8 @@
 export { buildCompletions } from "./build.js";
 export type { CompletionCtx } from "./detect-context.js";
+// The CEL half on its own, for a host completing an expression that is not in a
+// YAML document: studio's schema form edits a `!cel` body in a field, so it has
+// the site's address directly and nothing to detect a context from.
+// `buildCompletions` stays the entry point for a document plus a cursor.
+export { celCompletions } from "./cel-completions.js";
+export type { CelCompletionTarget } from "./cel-completions.js";

package/src/diagnostics/graph-diagnostics.ts

@@ -19,7 +19,7 @@ import { findPositions } from "./find-positions.js";
  * 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.
+ * VS Code, and telo studio agree on exactly what is compromised.
  */
 export function compromisedFiles(graph: LoadedGraph): Set<string> {
   const entrySource = graph.entry.owner.source;
@@ -50,7 +50,7 @@ export function compromisedFiles(graph: LoadedGraph): Set<string> {
  * 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
+ * telo studio 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.
  */