@xano/xanoscript-language-server 12.16.0 → 12.16.2

package/lexer/realtime_server_trigger.js

@@ -11,10 +11,14 @@ export const RealtimeServerTriggerToken = createTokenByName(
 );
 
 // "realtime_server" (parent-reference keyword used by realtimeServerClause).
-// longer_alt points at the trigger token so `realtime_server_trigger` wins
-// over the shorter `realtime_server` prefix.
+// longer_alt lists the trigger token so `realtime_server_trigger` wins over the
+// shorter `realtime_server` prefix, AND Identifier so a name that merely EXTENDS
+// the keyword (e.g. `realtime_server_0`, the default scaffold name) tokenizes as
+// one identifier instead of keyword + leftover `_0` (DEV-7582). longer_alt is not
+// transitive, so Identifier must be listed here directly — matching the
+// [ServerDetailsToken, Identifier] precedent in channel.js.
 export const RealtimeServerToken = createTokenByName("realtime_server", {
-  longer_alt: RealtimeServerTriggerToken,
+  longer_alt: [RealtimeServerTriggerToken, Identifier],
   categories: [Identifier], // could also be an identifier
 });
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xano/xanoscript-language-server",
-  "version": "12.16.0",
+  "version": "12.16.2",
   "description": "Language Server Protocol implementation for XanoScript",
   "type": "module",
   "main": "server.js",

package/parser/clauses/historyClause.js

@@ -1,8 +1,22 @@
 import { EqualToken } from "../../lexer/control.js";
+import { IntegerLiteral } from "../../lexer/literal.js";
 import { HistoryToken } from "../../lexer/tokens.js";
 
 /**
  * Parses the history clause.
+ *
+ * `history` mirrors the backend serializer (cloud-client
+ * helper/script/transform via `Transform::onSchemaRequestHistory`): the value is
+ * `false` (disabled), `"inherit"` (hand-authored sentinel), `"all"` (unbounded),
+ * or ANY non-negative integer message limit — not a fixed set of magic numbers.
+ * It is split across two OR branches because `schemaParseEnumFn` refuses an enum
+ * that mixes constants (`false`/`"inherit"`/`"all"`) with a generic numeric type:
+ * an integer literal is consumed directly, every other value by the sentinel
+ * enum (which keeps emitting the existing "must be one of …" error). The limit
+ * is an integer message count, so a float is intentionally NOT accepted.
+ * `IGNORE_AMBIGUITIES` steers an integer literal to the number branch, since both
+ * branches can begin with one.
+ *
  * @param {import('../base_parser.js').XanoBaseParser} $
  */
 export function historyClause($) {
@@ -10,8 +24,19 @@ export function historyClause($) {
     $.sectionStack.push("historyClause");
     const parent = $.CONSUME(HistoryToken); // "history"
     $.CONSUME(EqualToken); // "="
-    $.SUBRULE($.schemaParseEnumFn, {
-      ARGS: [parent, [false, "inherit", 0, 10, 100, 1000, 10000, "all"]],
+    $.OR({
+      IGNORE_AMBIGUITIES: true,
+      DEF: [
+        // any non-negative integer message limit (e.g. 50, 100, 250)
+        { ALT: () => $.CONSUME(IntegerLiteral) },
+        // the non-numeric sentinels: false | "inherit" | "all"
+        {
+          ALT: () =>
+            $.SUBRULE($.schemaParseEnumFn, {
+              ARGS: [parent, [false, "inherit", "all"]],
+            }),
+        },
+      ],
     });
 
     $.sectionStack.pop();

package/parser/message_parser.js

@@ -10,6 +10,8 @@ export function messageDeclaration($) {
     let hasChannel = false;
     let hasDeliverTo = false;
     let hasDescription = false;
+    let hasDocs = false;
+    let hasActive = false;
     let hasGuid = false;
     let hasHistory = false;
     let hasInput = false;
@@ -79,6 +81,24 @@ export function messageDeclaration($) {
             $.SUBRULE($.descriptionFieldAttribute);
           },
         },
+        {
+          // backend Message.php `encode()` emits `docs = "..."` for a
+          // documented message; round-tripped by `decode()`. See DEV-7620.
+          GATE: () => !hasDocs,
+          ALT: () => {
+            hasDocs = true;
+            $.SUBRULE($.docsFieldAttribute);
+          },
+        },
+        {
+          // backend Message.php `encode()` emits `active = false` for a
+          // disabled message; mirrors the sibling `channel` declaration.
+          GATE: () => !hasActive,
+          ALT: () => {
+            hasActive = true;
+            $.SUBRULE($.activeFieldAttribute);
+          },
+        },
         {
           GATE: () => !hasGuid,
           ALT: () => {
@@ -147,26 +167,12 @@ export function messageDeclaration($) {
       );
     }
 
-    if (!hasInput) {
-      $.addMissingError(
-        parent,
-        `{} ${nameToken.image} is missing an input clause`,
-      );
-    }
-
-    if (!hasStack) {
-      $.addMissingError(
-        parent,
-        `{} ${nameToken.image} is missing a stack clause`,
-      );
-    }
-
-    if (!hasResponse) {
-      $.addMissingError(
-        parent,
-        `{} ${nameToken.image} is missing a response clause`,
-      );
-    }
+    // input/stack/response are OPTIONAL on a message: a realtime v2 message is
+    // created config-only (its Stack is generated server-side after save), so a
+    // scaffold carrying only realtime_server/channel/deliver_to/description/history
+    // must be diagnostic-clean. Mirrors channel_parser.js (requires realtime_server
+    // only). When present, these clauses are still fully parsed + validated by the
+    // OR2 alternatives above.
 
     $.MANY1(() => $.CONSUME1(NewlineToken)); // optional new line
     $.CONSUME(RCurly); // "}"

package/parser/realtime_channel_parser.js

@@ -32,7 +32,11 @@ export function realtimeChannelDeclaration($) {
           "settings?": {
             anonymous_clients: "[boolean]",
             nested_channels: "[boolean]",
-            message_history: [0, 25, 50, 100, 250, 1000],
+            // The CLI pull emits `message_history: history ?? 0` (an arbitrary
+            // integer — see cloud-client RealtimeChannel.php `onSettings`), so
+            // accept any numeric value rather than a fixed enum. Kept typed
+            // ("[number]") so a non-numeric value still surfaces a diagnostic.
+            message_history: "[number]",
             auth_channel: "[boolean]",
             presence: "[boolean]",
           },