@omfalos/mokosh 0.2.0 → 0.3.0

package/dist/index.d.mts

@@ -357,8 +357,9 @@ interface FunctionCallInfo {
  * field matches `functionName`. Callees are found by looking at the defining
  * file's `callEdges` for edges whose `from` field matches `functionName`.
  *
- * Call edges are populated only for TypeScript/JavaScript files. Functions in
- * other language files will return empty `callers` and `callees` arrays.
+ * Call edges are populated only for TypeScript/JavaScript, Go, and Python files
+ * (see `CALL_EDGE_TYPES` in `../language-support`). Functions in other language
+ * files will return empty `callers` and `callees` arrays.
  *
  * @param {Graph} graph - The import graph that carries `callEdges` on each node.
  * @param {string} functionName - Exact name of the function to look up.
@@ -956,7 +957,8 @@ interface FindComplexFunctionsOptions {
 }
 /**
  * @description Scans every file's per-function complexity breakdown and returns functions/methods
- *   at or above the given threshold, sorted worst-first. TypeScript/JavaScript only.
+ *   at or above the given threshold, sorted worst-first. Populated for TypeScript/JavaScript, Go,
+ *   and Python.
  * @param graph - The graph to scan.
  * @param options - `metric` picks which score to threshold/sort on (default `cognitiveComplexity`); `threshold` is the minimum score to include (default 10); `limit` caps the results (default 20).
  * @returns Matching functions, sorted worst-first.
@@ -1012,7 +1014,7 @@ declare function hasCoverageData(graph: Graph): boolean;
 
 /** Symbol-name lookup across the whole graph — generalizes queryCallGraph beyond TS/JS functions. */
 
-type SymbolPrecision = "call" | "import-symbol" | "file-level";
+type SymbolPrecision = "call" | "file-level";
 interface SymbolCaller {
     file: string;
     callerFunction: string;
@@ -1031,9 +1033,11 @@ interface SymbolMatch {
 /**
  * @description Finds every file that exports a symbol by name, with the best available
  *   usage info per match. Precision depends on what the defining file's language parser
- *   tracks: TS/JS gets function-level callers via call edges, Python gets named-import
- *   tracking, everything else falls back to whole-file dependents (import-level, not
- *   symbol-level — the file might not even use this specific export).
+ *   tracks: TS/JS, Go, and Python get function-level callers via call edges (`"call"`);
+ *   everything else falls back to whole-file dependents (`"file-level"` — import-level, not
+ *   symbol-level, since the file might not even use this specific export). Coverage still
+ *   differs across the `"call"` languages: TS/JS tracks any directly imported symbol, Go only
+ *   package-qualified calls, Python only bare calls to `from <module> import <name>` symbols.
  * @param graph - The graph to search.
  * @param name - Exact export name to look up.
  * @returns One entry per file that exports `name`; empty if no file does (including

package/dist/index.d.ts

@@ -357,8 +357,9 @@ interface FunctionCallInfo {
  * field matches `functionName`. Callees are found by looking at the defining
  * file's `callEdges` for edges whose `from` field matches `functionName`.
  *
- * Call edges are populated only for TypeScript/JavaScript files. Functions in
- * other language files will return empty `callers` and `callees` arrays.
+ * Call edges are populated only for TypeScript/JavaScript, Go, and Python files
+ * (see `CALL_EDGE_TYPES` in `../language-support`). Functions in other language
+ * files will return empty `callers` and `callees` arrays.
  *
  * @param {Graph} graph - The import graph that carries `callEdges` on each node.
  * @param {string} functionName - Exact name of the function to look up.
@@ -956,7 +957,8 @@ interface FindComplexFunctionsOptions {
 }
 /**
  * @description Scans every file's per-function complexity breakdown and returns functions/methods
- *   at or above the given threshold, sorted worst-first. TypeScript/JavaScript only.
+ *   at or above the given threshold, sorted worst-first. Populated for TypeScript/JavaScript, Go,
+ *   and Python.
  * @param graph - The graph to scan.
  * @param options - `metric` picks which score to threshold/sort on (default `cognitiveComplexity`); `threshold` is the minimum score to include (default 10); `limit` caps the results (default 20).
  * @returns Matching functions, sorted worst-first.
@@ -1012,7 +1014,7 @@ declare function hasCoverageData(graph: Graph): boolean;
 
 /** Symbol-name lookup across the whole graph — generalizes queryCallGraph beyond TS/JS functions. */
 
-type SymbolPrecision = "call" | "import-symbol" | "file-level";
+type SymbolPrecision = "call" | "file-level";
 interface SymbolCaller {
     file: string;
     callerFunction: string;
@@ -1031,9 +1033,11 @@ interface SymbolMatch {
 /**
  * @description Finds every file that exports a symbol by name, with the best available
  *   usage info per match. Precision depends on what the defining file's language parser
- *   tracks: TS/JS gets function-level callers via call edges, Python gets named-import
- *   tracking, everything else falls back to whole-file dependents (import-level, not
- *   symbol-level — the file might not even use this specific export).
+ *   tracks: TS/JS, Go, and Python get function-level callers via call edges (`"call"`);
+ *   everything else falls back to whole-file dependents (`"file-level"` — import-level, not
+ *   symbol-level, since the file might not even use this specific export). Coverage still
+ *   differs across the `"call"` languages: TS/JS tracks any directly imported symbol, Go only
+ *   package-qualified calls, Python only bare calls to `from <module> import <name>` symbols.
  * @param graph - The graph to search.
  * @param name - Exact export name to look up.
  * @returns One entry per file that exports `name`; empty if no file does (including