@golemui/gui-mcp 1.5.1 → 1.6.0-rc.0

package/CHANGELOG.md

@@ -1,3 +1,14 @@
+## 1.5.1 (2026-09-23)
+
+### 🩹 Fixes
+
+- **gui-mcp:** declare @golemui/dx as a dependency ([5d43a4f0](https://github.com/golemui/golemui/commit/5d43a4f0))
+- **gui-components:** show a restored mid-upload file as failed without emitting a change at mount ([f3597275](https://github.com/golemui/golemui/commit/f3597275))
+
+### ❤️ Thank You
+
+- Raúl Jiménez @Elecash
+
 ## 1.5.1-rc.0 (2026-09-23)
 
 ### 🩹 Fixes

package/README.md

@@ -98,21 +98,26 @@ like missing `$form.` prefixes, single `=` in equality checks, and unbalanced br
 
 ### `json_generate_from_schema`
 
-Maps a JSON Schema (the form-data shape, e.g. a Zod-derived schema) into a GolemUI
-form definition. Handles strings (with `format` → specialized widgets), numbers,
-booleans, enums, nested objects, and arrays of objects. The result is validated before
-being returned, so you get a guaranteed-correct form or an explicit list of what could
-not be mapped.
+Converts a JSON Schema (the form-data shape, e.g. a Zod-derived schema) into a GolemUI
+form definition, with `fromJsonSchema` from `@golemui/schemas/json-schema` and the gui
+preset from `@golemui/gui-schemas/json-schema`. It handles formats, enums, local `$ref`,
+`allOf`, nested objects, arrays, discriminated `oneOf`/`anyOf`, and `if/then/else` and
+`dependent*` as conditions and form states. The result is validated before it is returned.
 
-**Input:** `{ jsonSchema, submitAction?, submitLabel?, layout? }`
+`diagnostics` lists what the form cannot express exactly, each with a `severity`, a `code`,
+the data `path` and the JSON `pointer` into the input. `unmapped` repeats its errors and
+warnings as `{ path, reason }`. `rules` and `overrides` choose other widgets: see the
+`@golemui/schemas` README.
+
+**Input:** `{ jsonSchema, submitAction?, submitLabel?, layout?, rules?, overrides? }`
 
 ### `json_generate_from_openapi`
 
-Resolves an OpenAPI 3.x operation (e.g. `"POST /users"` or an `operationId`), dereferences
-its request body schema, and emits a validated GolemUI form. Falls back to operation
-parameters when no JSON request body is present.
+Resolves an OpenAPI 3.x operation (e.g. `"POST /users"` or an `operationId`) and converts
+its JSON request body, with its `$ref`s into the document, like `json_generate_from_schema`.
+Falls back to the operation parameters when there is no object request body.
 
-**Input:** `{ document | documentUrl, operation, submitAction?, submitLabel? }`
+**Input:** `{ document | documentUrl, operation, submitAction?, submitLabel?, rules?, overrides? }`
 
 ### `json_get_widget_spec`
 
@@ -184,10 +189,10 @@ const result = validateFormDefinition({ formDefinition: myForm });
 if (!result.valid) console.error(result.errors);
 
 // Generate a form from a JSON Schema
-const { form, unmapped } = generateFromJsonSchema({ jsonSchema: mySchema });
+const { formDefinition, diagnostics } = generateFromJsonSchema({ jsonSchema: mySchema });
 
 // Generate a form from an OpenAPI spec
-const { form } = await generateFromOpenapi({
+const { formDefinition: userForm } = await generateFromOpenapi({
   documentUrl: 'https://example.com/openapi.json',
   operation: 'POST /users',
 });

package/cli.js

@@ -5,8 +5,8 @@ import { fileURLToPath } from "node:url";
 import { Server } from "@modelcontextprotocol/sdk/server/index.js";
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 import { ListToolsRequestSchema, CallToolRequestSchema } from "@modelcontextprotocol/sdk/types.js";
-import { d as checkDxCode, r as resolveDxFramework, f as listDxFactoriesCatalog, b as DX_LIST_FACTORIES_TOOL, g as getDxSpec, a as DX_GET_SPEC_TOOL, D as DX_CHECK_CODE_TOOL } from "./list-dx-factories-D3u4qsn1.js";
-import { v as validateFormDefinition, c as JSON_VALIDATE_FORM_DEFINITION_TOOL, g as generateFromJsonSchema, a as JSON_GENERATE_FROM_SCHEMA_TOOL, d as generateFromOpenapi, J as JSON_GENERATE_FROM_OPENAPI_TOOL, f as getWidgetSpec, b as JSON_GET_WIDGET_SPEC_TOOL, e as getConcept, G as GET_CONCEPT_TOOL } from "./get-concept-MFKfeD4D.js";
+import { d as checkDxCode, r as resolveDxFramework, f as listDxFactoriesCatalog, b as DX_LIST_FACTORIES_TOOL, g as getDxSpec, a as DX_GET_SPEC_TOOL, D as DX_CHECK_CODE_TOOL } from "./list-dx-factories-BKx43VHj.js";
+import { v as validateFormDefinition, c as JSON_VALIDATE_FORM_DEFINITION_TOOL, g as generateFromJsonSchema, a as JSON_GENERATE_FROM_SCHEMA_TOOL, d as generateFromOpenapi, J as JSON_GENERATE_FROM_OPENAPI_TOOL, f as getWidgetSpec, b as JSON_GET_WIDGET_SPEC_TOOL, e as getConcept, G as GET_CONCEPT_TOOL } from "./get-concept-BqdUfdaO.js";
 const USAGE = `Usage: golemui-mcp [command]
 
 Validate GolemUI forms from the command line (no MCP client needed).
@@ -110,7 +110,7 @@ const dxTools = [
   defineTool(DX_GET_SPEC_TOOL, getDxSpec),
   defineTool(DX_CHECK_CODE_TOOL, checkDxCode)
 ];
-const JSON_INSTRUCTIONS = '1. Starting from an existing schema? Use a generator — both return a pre-validated definition, so check the returned `unmapped` list and surface anything left over to the user. For a raw JSON Schema (e.g. an API request body), call `json_generate_from_schema`. For an OpenAPI 3.x spec, call `json_generate_from_openapi`: pass `operation` as "METHOD /path" (e.g. "POST /users") or an exact operationId, plus the spec as a parsed `document` or a `documentUrl` to fetch — it resolves the operation\'s request body, dereferences `$ref`s, and falls back to the operation\'s parameters when there is no request body.\n2. Building or editing by hand? Look up a single widget with `json_get_widget_spec` (its `kind`, `props`, and `validator` shape), and cross-cutting behavior that spans widgets — conditional rendering, per-state prop overrides, validation rules and error messages — with `get_concept`. Before writing a mandatory checkbox or gating a button on `$formIsInvalid`, call `get_concept({ concept: "validation" })` — both have non-obvious traps.\n3. ALWAYS finish by calling `json_validate_form_definition`. It checks the definition against the bundled JSON Schemas and returns `{ valid, errors, warnings, expressionWarnings }`. Treat `errors` as blocking: fix them and re-validate until `valid` is true. `warnings` (likely-custom widgets) and `expressionWarnings` (linted reactive expressions) are advisory — surface them, but they do not flip `valid`.\n\n';
+const JSON_INSTRUCTIONS = '1. Starting from an existing schema? Use a generator — both return a pre-validated definition, so check the returned `unmapped` list and surface anything left over to the user. For a raw JSON Schema (e.g. an API request body), call `json_generate_from_schema`. For an OpenAPI 3.x spec, call `json_generate_from_openapi`: pass `operation` as "METHOD /path" (e.g. "POST /users") or an exact operationId, plus the spec as a parsed `document` or a `documentUrl` to fetch — it resolves the operation\'s request body, dereferences `$ref`s, and falls back to the operation\'s parameters when there is no request body. Both also return `diagnostics` (severity, code, path, pointer), and both take optional `overrides` (widget fields by data path, e.g. `{ "address.street": { "widget": "textarea" } }`) and `rules` to choose other widgets.\n2. Building or editing by hand? Look up a single widget with `json_get_widget_spec` (its `kind`, `props`, and `validator` shape), and cross-cutting behavior that spans widgets — conditional rendering, per-state prop overrides, validation rules and error messages — with `get_concept`. Before writing a mandatory checkbox or gating a button on `$formIsInvalid`, call `get_concept({ concept: "validation" })` — both have non-obvious traps.\n3. ALWAYS finish by calling `json_validate_form_definition`. It checks the definition against the bundled JSON Schemas and returns `{ valid, errors, warnings, expressionWarnings }`. Treat `errors` as blocking: fix them and re-validate until `valid` is true. `warnings` (likely-custom widgets) and `expressionWarnings` (linted reactive expressions) are advisory — surface them, but they do not flip `valid`.\n\n';
 const jsonTools = [
   defineTool(JSON_VALIDATE_FORM_DEFINITION_TOOL, validateFormDefinition),
   defineTool(JSON_GENERATE_FROM_SCHEMA_TOOL, generateFromJsonSchema),