@xano/xanoscript-language-server 12.23.0 → 12.24.0

package/lexer/tokens.js

@@ -295,7 +295,7 @@ export const HistoryToken = createTokenByName("history", {
   categories: [Identifier], // could also be an identifier
 });
 
-// `mesh0 = {logging, statements}` on objects and containers.
+// `mesh0 = {logging}` on objects and containers.
 export const Mesh0Token = createTokenByName("mesh0", {
   longer_alt: Identifier,
   categories: [Identifier], // could also be an identifier

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xano/xanoscript-language-server",
-  "version": "12.23.0",
+  "version": "12.24.0",
   "description": "Language Server Protocol implementation for XanoScript, the language of Xano backends",
   "keywords": [
     "xano",

package/parser/branch_parser.js

@@ -57,7 +57,7 @@ export function branchDeclaration($) {
             "prompt?": historyValues,
             "resource?": historyValues,
           },
-          // Strict whitelist of run types, each `{logging, statements}`.
+          // Strict whitelist of run types, each `{logging}`.
           // The platform writes only the types that differ from the
           // default, and no block at all when none do.
           "mesh0?": {

package/parser/clauses/mesh0Clause.js

@@ -2,26 +2,25 @@ import { EqualToken } from "../../lexer/control.js";
 import { Mesh0Token } from "../../lexer/tokens.js";
 
 /**
- * The value set of one mesh0 setting, `{logging, statements}`, shared by the
+ * The value set of one mesh0 setting, `{logging}`, shared by the
  * object/container `mesh0 = {...}` clause and each run type of a branch
  * document's `mesh0` block (`branch_parser.js`).
  *
  * Mirrors the platform's mesh0 settings: `logging` is the trace detail
- * (`"inherit"` defers to the next level), `statements` the per-run statement
- * span cap. Unlimited is written `"all"`, as `history` writes it; the platform
- * stores it as `-1`. Both keys are optional, and a missing one inherits.
+ * (`"inherit"` defers to the next level) and is required. The per-run
+ * statement span cap is not a mesh0 key; the platform takes it from the
+ * request-history `history` setting, so a `statements` key is invalid.
  */
 export const MESH0_SETTING_SCHEMA = {
-  "logging?": ["inherit", "minimal", "light", "full"],
-  "statements?": [100, 1000, 10000, "all"],
+  logging: ["inherit", "minimal", "light", "full"],
 };
 
 /**
- * Parses the `mesh0 = {logging: "light", statements: 1000}` setting of an
- * object (query, function, task, tool, middleware, trigger, prompt, resource)
- * or a container (api_group, mcp_server, channel, realtime_server). It sits
- * beside `history`. A container presents the same two keys; the platform maps
- * them to its type-prefixed fields (`query_logging`, `tool_statements`, ...).
+ * Parses the `mesh0 = {logging: "light"}` setting of an object (query,
+ * function, task, tool, middleware, trigger, prompt, resource) or a container
+ * (api_group, mcp_server, channel, realtime_server). It sits beside
+ * `history`. A container presents the same key; the platform maps it to its
+ * type-prefixed field (`query_logging`, `tool_logging`, ...).
  *
  * @param {import('../base_parser.js').XanoBaseParser} $
  */
@@ -31,19 +30,8 @@ export function mesh0Clause($) {
     const parent = $.CONSUME(Mesh0Token); // "mesh0"
     $.CONSUME(EqualToken); // "="
 
-    const captured = {};
     $.SUBRULE($.schemaParseObjectFn, {
-      ARGS: [parent, MESH0_SETTING_SCHEMA, captured],
-    });
-
-    // Both keys are optional, but an empty setting says nothing.
-    $.ACTION(() => {
-      if (Object.keys(captured).length === 0) {
-        $.addMissingError(
-          parent,
-          "{} requires at least one of: logging, statements",
-        );
-      }
+      ARGS: [parent, MESH0_SETTING_SCHEMA],
     });
 
     $.sectionStack.pop();