@xano/xanoscript-language-server 12.20.1 → 12.22.0

package/parser/policy/catalogue.js

@@ -9,7 +9,7 @@
  * language server checks the policy's block shape only.
  *
  * A host fills it:
- *   - Studio sends its own live answer (`source: "live"`); a check-level problem is then an
+ *   - The Xano editor sends its own live answer (`source: "live"`); a check-level problem is then an
  *     error, because the instance refuses the same save.
  *   - The Node server and offline tools load the generated snapshot (`catalogueSnapshot.js`,
  *     `source: "snapshot"`); a check-level problem is then a warning, because the snapshot can
@@ -30,7 +30,7 @@ let version = 0;
 
 /**
  * Replace the catalogue.
- * @param {Object|Object[]|null} catalogue `{items, document}` as the platform serves it, Studio's
+ * @param {Object|Object[]|null} catalogue `{items, document}` as the platform serves it, the editor's
  *   `{checks, document}`, or a bare list of checks; null clears it
  * @param {{source?: "live"|"snapshot", generatedAt?: string|null}} [options]
  */

package/parser/policy/policyLiteral.js

@@ -45,7 +45,7 @@ export const isA = (token, type) => !!token && tokenMatcher(token, type);
 /** A catalogue entry's own property, never an inherited one (`constructor`, `toString`). */
 export const own = (object, key) => object && Object.hasOwn(object, key) ? object[key] : undefined;
 
-/** Native Parser::stripQuotes: double quotes use C escapes, single quotes only \\ and \'. */
+/** As the platform reads a string: double quotes use C escapes, single quotes only \\ and \'. */
 export function policyStringValue(image) {
   if (image.startsWith('"""') || image.startsWith("'''")) {
     return image.slice(3, -3).replace(/^\r?\n/, "").replace(/\r?\n[ ]*$/, "");

package/parser/policy/validatePolicyRule.js

@@ -6,8 +6,7 @@ import { policyLiteralValue } from "./policyLiteral.js";
  * Everything here is read from the catalogue the host loaded (see `catalogue.js`): the check
  * ids, each check's params with their types, closed value sets, nested fields, `required`,
  * `requires_one_of`, `minimum` and `non_empty`, and the scope fields that apply to it. Nothing
- * names a check. The findings are worded like the platform's refusals (`Registry::validateParams`,
- * `coerce`, `unknownCheck`) without their `rule[i] ("KEY.Rn"): params:` prefix, since a diagnostic
+ * names a check. The findings are worded like the platform's refusals without their `rule[i] ("KEY.Rn"): params:` prefix, since a diagnostic
  * already points at the place; they are a preview, and the platform's own answer on save decides.
  * Where the platform stops at the first refusal, this reports every problem, one per param.
  *
@@ -15,17 +14,17 @@ import { policyLiteralValue } from "./policyLiteral.js";
  * holds at most `STRING_MAX_LENGTH` characters, and a name longer than `NEAREST_MAX_LENGTH` bytes
  * gets no near miss.
  *
- * Check-specific rules the catalogue does not publish (`Check::validate`, `authoredRefusal`,
+ * Check-specific rules the catalogue does not publish (per-check validation,
  * renamed ids and params, statement wildcards) are left to the platform.
  *
  * Whether a value is a literal at all, and duplicate names, are the block's shape, not the
  * catalogue's: the parser reports those (policy_parser.js) and this skips such values.
  */
 
-/** `Registry::STRING_MAX_LENGTH`: the longest string a string or string[] param may hold, in characters. */
+/** The platform's limit on the longest string a string or string[] param may hold, in characters. */
 const STRING_MAX_LENGTH = 1024;
 
-/** `Registry::NEAREST_MAX_LENGTH`: the longest name, in bytes, a near miss is looked for. */
+/** The platform's limit on the longest name, in bytes, a near miss is looked for. */
 const NEAREST_MAX_LENGTH = 128;
 
 /** Edit distance, as PHP's `levenshtein` (insert, delete and replace all cost 1). */
@@ -49,7 +48,7 @@ function levenshtein(a, b) {
 }
 
 /**
- * The closest names to a misspelling, nearest first, at most two (`Registry::nearest`): within
+ * The closest names to a misspelling, nearest first, at most two, as the platform suggests them: within
  * three edits, or one containing the other. A name longer than `NEAREST_MAX_LENGTH` bytes gets
  * none, since edit distance costs the product of the two lengths per candidate.
  * @param {string} wanted
@@ -79,7 +78,7 @@ export function didYouMean(name, candidates) {
   return near.length ? `Did you mean ${near.map((n) => `"${n}"`).join(" or ")}? ` : "";
 }
 
-/** `Registry::provided`: set when not null/false, not an empty or blank string, not an empty list or object. */
+/** Whether a param counts as provided: set when not null/false, not an empty or blank string, not an empty list or object. */
 function provided(value) {
   if (value === null || value === undefined || value === false) return false;
   if (typeof value === "string") return value.trim() !== "";
@@ -89,7 +88,7 @@ function provided(value) {
 }
 
 /**
- * A param's value as the platform validates it (`Registry::validateParams`): one left out, or written
+ * A param's value as the platform validates it: one left out, or written
  * as `null` when its type is not `any`, is its default.
  */
 const inForce = (literal, schema, name) =>
@@ -107,7 +106,7 @@ export function unknownCheckMessage(id, ids) {
 }
 
 /**
- * `Registry::coerce`: whether a value has its param's declared type and values.
+ * Whether a value has its param's declared type and values.
  * @returns {{token: Object, message: string}|null}
  */
 function coerce(node, spec, checkId, name) {
@@ -124,7 +123,7 @@ function coerce(node, spec, checkId, name) {
       if (!whole || (minimum !== undefined && node.value < minimum)) {
         return fail(`be a whole number${minimum !== undefined ? ` of at least ${minimum}` : ""}`);
       }
-      // `Registry::INTEGER_MAX`: past 2^53 - 1 a whole number is no longer exact.
+      // The platform's integer limit: past 2^53 - 1 a whole number is no longer exact.
       if (Math.abs(node.value) > Number.MAX_SAFE_INTEGER) {
         return fail(`be a whole number no larger than ${Number.MAX_SAFE_INTEGER}`);
       }
@@ -188,7 +187,7 @@ function closedProperties(spec) {
 
 /**
  * Why a set scope field cannot change what a rule of this check selects, or null when it can,
- * read from the check's published `scope_fields` (the same reading as Studio's rule form).
+ * read from the check's published `scope_fields` (the same reading as the Xano editor's rule form).
  */
 function inapplicableScope(check, name, literal) {
   const field = (check.scope_fields ?? []).find((item) => item?.name === name);

package/parser/policy_parser.js

@@ -21,10 +21,10 @@ import { didYouMean, validatePolicyRule } from "./policy/validatePolicyRule.js";
 //     rule { <field> = <literal> } # repeating; `check` names a catalogue item, `params` its params
 //   }
 //
-// with the comment, named-rule and literal-value rules of cloud-client's Script.php. It knows no
+// with the comment, named-rule and literal-value rules the platform enforces. It knows no
 // field: which fields a policy and a rule may set, their types, value sets and defaults, the retired
 // fields and reserved blocks, the key pattern and when a rule is required all come from the
-// catalogue's `document` (helper/mvp/policy/Document.php), and every check from its `items`. With no
+// catalogue's `document`, and every check from its `items`. With no
 // catalogue loaded, only the shape is checked. See parser/policy/catalogue.js.
 
 /** The platform's refusal of a named rule, after its `rule[<i>]: ` prefix. */
@@ -287,7 +287,7 @@ function fieldProblem(name, node, spec) {
 }
 
 /**
- * A rule's params: an object of literal values (Script::literal; a name written twice is already
+ * A rule's params: an object of literal values (a name written twice is already
  * reported by the object grammar). The catalogue then says what the object may hold.
  */
 function checkParamsShape(node, report) {

package/parser/realtime_channel_parser.js

@@ -33,7 +33,7 @@ export function realtimeChannelDeclaration($) {
             anonymous_clients: "[boolean]",
             nested_channels: "[boolean]",
             // The CLI pull emits `message_history: history ?? 0` (an arbitrary
-            // integer — see cloud-client RealtimeChannel.php `onSettings`), so
+            // integer), 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]",