@xano/developer-mcp 1.0.48 → 1.0.50

package/dist/xanoscript.js

@@ -178,7 +178,7 @@ export const XANOSCRIPT_DOCS_V2 = {
     },
     workspace: {
         file: "workspace.md",
-        applyTo: ["workspace.xs"],
+        applyTo: ["workspace/**/*.xs"],
         description: "Workspace-level settings: environment variables, preferences, realtime",
     },
 };

package/dist/xanoscript_docs/types.md

@@ -325,6 +325,19 @@ input {
 }
 ```
 
+### Required Fields Also Reject Empty Strings
+
+> **Important for testing:** A required `text` field (no `?` after the name) rejects both `null` **and** empty strings (`""`). Sending `""` triggers a platform-level validation error **before your stack runs** — your preconditions and custom error handling never execute.
+
+| Value sent | `text name` | `text? name` | `text name?` | `text? name?` |
+|------------|-------------|--------------|--------------|---------------|
+| `"Alice"` | ✅ valid | ✅ valid | ✅ valid | ✅ valid |
+| `""` | ❌ validation error | ❌ validation error | ✅ valid (empty) | ✅ valid (empty) |
+| `null` | ❌ validation error | ✅ valid | ❌ validation error | ✅ valid |
+| *(omitted)* | ❌ validation error | ❌ validation error | ✅ valid | ✅ valid |
+
+To test the "empty input" scenario for a text field, the field must be declared optional (`text name?`). Testing a required field with `""` will always produce a validation error — never your custom logic.
+
 ---
 
 ## Foreign Key References

package/dist/xanoscript_docs/unit-testing.md

@@ -311,6 +311,65 @@ function "validate_age" {
 
 ---
 
+## Common Mistakes
+
+### Testing Required Fields with Empty Strings
+
+A required input field (no `?` after the name) rejects both `null` and empty strings at the platform level — **before your stack runs**. Writing a test that sends `""` to a required field will always get a validation error, never your custom precondition or error logic.
+
+❌ **Wrong — will always throw a validation error, not your custom error:**
+```xs
+function "create_user" {
+  input { text name }  // required: rejects null AND ""
+  stack {
+    precondition ($input.name != "") {
+      error_type = "inputerror"
+      error = "Name cannot be blank"
+    }
+  }
+  response = { ok: true }
+
+  // This test gets a validation error from the input layer, not "Name cannot be blank"
+  test "rejects empty name" {
+    input = { name: "" }
+    expect.to_throw { value = "Name cannot be blank" }
+  }
+}
+```
+
+✅ **Correct — use an optional field if you need to test the empty/omitted case:**
+```xs
+function "create_user" {
+  input { text name? }  // optional: accepts "", null, or omission
+  stack {
+    precondition ($input.name != null && $input.name != "") {
+      error_type = "inputerror"
+      error = "Name cannot be blank"
+    }
+  }
+  response = { ok: true }
+
+  test "rejects empty name" {
+    input = { name: "" }
+    expect.to_throw { value = "Name cannot be blank" }
+  }
+
+  test "rejects null name" {
+    input = { name: null }
+    expect.to_throw { value = "Name cannot be blank" }
+  }
+
+  test "accepts valid name" {
+    input = { name: "Alice" }
+    expect.to_equal ($response.ok) { value = true }
+  }
+}
+```
+
+For a full breakdown of what each required/optional/nullable combination accepts, see `xanoscript_docs({ topic: "types" })`.
+
+---
+
 ## Complete Example
 
 ```xs

package/dist/xanoscript_docs/workflow-tests.md

@@ -323,6 +323,7 @@ workflow_test "comprehensive_test" {
 4. **Keep tests independent** — Each workflow test should be self-contained and not depend on other tests
 5. **Use `function.call`, not `function.run`** — `function.call` handles errors so that `expect` assertions work correctly. `function.run` is for calling functions outside of workflow tests
 6. **Use assertions over preconditions** — Prefer `expect.*` assertions for clearer test intent
+7. **Don't test required fields with empty strings** — Required inputs reject both `null` and `""` at the platform level before your stack runs. If you send `""` to a required `text` field, you'll always get a platform validation error — never your custom logic. To test the empty/blank case, the input must be declared optional (`text name?`). See `xanoscript_docs({ topic: "types" })` for the full breakdown.
 
 ---
 

package/dist/xanoscript_docs/workspace.md

@@ -1,5 +1,5 @@
 ---
-applyTo: "workspace.xs"
+applyTo: "workspace/**/*.xs"
 ---
 
 # Workspace Configuration
@@ -21,6 +21,7 @@ workspace "<name>" {
 ### Attributes
 | Attribute | Type | Required | Description |
 |-----------|------|----------|-------------|
+| `name` | text | **Yes** | Workspace name (matches the filename, e.g. `workspace/my_project.xs` → `"my_project"`) |
 | `description` | text | No | Human-readable workspace description |
 | `env` | object | No | Environment variable definitions |
 | `acceptance` | object | No | Terms and acceptance settings |
@@ -171,7 +172,7 @@ workspace "ecommerce_platform" {
 
 ## File Location
 
-Workspace configuration is stored in `workspace.xs` at the root of your project.
+Workspace configuration is stored as `workspace/<name>.xs`, where `<name>` matches the name declared in the `workspace` block.
 
 ```
 project/

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xano/developer-mcp",
-  "version": "1.0.48",
+  "version": "1.0.50",
   "description": "MCP server and library for Xano development - XanoScript validation, Meta API, Run API, and CLI documentation",
   "type": "module",
   "main": "dist/lib.js",