@ng-forge/dynamic-form-mcp 1.1.0-next.3 → 1.1.0-next.4

package/bin/ng-forge-mcp.js

@@ -8933,7 +8933,36 @@ validators: [{
 }]
 \`\`\`
 
-**Built-in Kinds:** required, email, min, max, minlength, maxlength, pattern`
+**Built-in Kinds:** required, email, min, max, minlength, maxlength, pattern
+
+## Template parameters
+
+String messages interpolate error params with \`{{param}}\`:
+
+\`\`\`typescript
+validationMessages: {
+  minLength: 'Must be at least {{requiredLength}} characters',
+  min: 'Must be at least {{min}}',
+  max: 'Must be at most {{max}}',
+  pattern: 'Does not match {{requiredPattern}}',
+}
+\`\`\`
+
+## Error-aware message functions (TypeScript configs only)
+
+Any \`validationMessages\` or \`defaultValidationMessages\` value can be a function \`(error: ValidationError) => DynamicText\` instead of a string. The function receives the validation error (its \`kind\` plus params such as \`maxLength\`), so an i18n layer gets the interpolation params natively:
+
+\`\`\`typescript
+validationMessages: {
+  maxLength: (error) => transloco.selectTranslate('validation.maxLength', {
+    requiredLength: 'maxLength' in error ? error.maxLength : undefined,
+  }),
+}
+\`\`\`
+
+A resolver may return static text, an \`Observable\`, or a \`Signal\`, and those stay reactive. Returning a plain string after synchronously reading a signal severs reactivity \u2014 return the \`Signal\`/\`Observable\` itself instead.
+
+**\u26A0\uFE0F Not JSON-serializable.** Function messages only work in TypeScript-authored configs. JSON-driven configs (and MCP-generated output) MUST use string templates with \`{{param}}\` interpolation.`
   },
   buttons: {
     brief: `**submit:** \`{ type: 'submit', key: 'submit', label: 'Submit' }\`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ng-forge/dynamic-form-mcp",
-  "version": "1.1.0-next.3",
+  "version": "1.1.0-next.4",
   "description": "MCP server for ng-forge dynamic forms - AI-assisted form schema generation",
   "type": "module",
   "license": "MIT",
@@ -54,11 +54,11 @@
     "zod-to-json-schema": "^3.23.0"
   },
   "devDependencies": {
-    "@ng-forge/dynamic-forms": "^1.1.0-next.3",
-    "@ng-forge/dynamic-forms-bootstrap": "^1.1.0-next.3",
-    "@ng-forge/dynamic-forms-ionic": "^1.1.0-next.3",
-    "@ng-forge/dynamic-forms-material": "^1.1.0-next.3",
-    "@ng-forge/dynamic-forms-primeng": "^1.1.0-next.3",
+    "@ng-forge/dynamic-forms": "^1.1.0-next.4",
+    "@ng-forge/dynamic-forms-bootstrap": "^1.1.0-next.4",
+    "@ng-forge/dynamic-forms-ionic": "^1.1.0-next.4",
+    "@ng-forge/dynamic-forms-material": "^1.1.0-next.4",
+    "@ng-forge/dynamic-forms-primeng": "^1.1.0-next.4",
     "tsx": "^4.19.0"
   }
 }

package/src/index.js

@@ -9010,7 +9010,36 @@ validators: [{
 }]
 \`\`\`
 
-**Built-in Kinds:** required, email, min, max, minlength, maxlength, pattern`
+**Built-in Kinds:** required, email, min, max, minlength, maxlength, pattern
+
+## Template parameters
+
+String messages interpolate error params with \`{{param}}\`:
+
+\`\`\`typescript
+validationMessages: {
+  minLength: 'Must be at least {{requiredLength}} characters',
+  min: 'Must be at least {{min}}',
+  max: 'Must be at most {{max}}',
+  pattern: 'Does not match {{requiredPattern}}',
+}
+\`\`\`
+
+## Error-aware message functions (TypeScript configs only)
+
+Any \`validationMessages\` or \`defaultValidationMessages\` value can be a function \`(error: ValidationError) => DynamicText\` instead of a string. The function receives the validation error (its \`kind\` plus params such as \`maxLength\`), so an i18n layer gets the interpolation params natively:
+
+\`\`\`typescript
+validationMessages: {
+  maxLength: (error) => transloco.selectTranslate('validation.maxLength', {
+    requiredLength: 'maxLength' in error ? error.maxLength : undefined,
+  }),
+}
+\`\`\`
+
+A resolver may return static text, an \`Observable\`, or a \`Signal\`, and those stay reactive. Returning a plain string after synchronously reading a signal severs reactivity \u2014 return the \`Signal\`/\`Observable\` itself instead.
+
+**\u26A0\uFE0F Not JSON-serializable.** Function messages only work in TypeScript-authored configs. JSON-driven configs (and MCP-generated output) MUST use string templates with \`{{param}}\` interpolation.`
   },
   buttons: {
     brief: `**submit:** \`{ type: 'submit', key: 'submit', label: 'Submit' }\`

package/src/tools/data/lookup-topics.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"lookup-topics.d.ts","sourceRoot":"","sources":["../../../../../../packages/dynamic-form-mcp/src/tools/data/lookup-topics.ts"],"names":[],"mappings":"AAAA,yBAAyB;AAEzB,4CAA4C;AAC5C,eAAO,MAAM,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE;IAAE,KAAK,EAAE,MAAM,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,CAy/ElE,CAAC;AAEF;;;GAGG;AACH,eAAO,MAAM,kBAAkB,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAiDrD,CAAC;AAEF,yCAAyC;AACzC,eAAO,MAAM,aAAa,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAuJhD,CAAC"}
+{"version":3,"file":"lookup-topics.d.ts","sourceRoot":"","sources":["../../../../../../packages/dynamic-form-mcp/src/tools/data/lookup-topics.ts"],"names":[],"mappings":"AAAA,yBAAyB;AAEzB,4CAA4C;AAC5C,eAAO,MAAM,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE;IAAE,KAAK,EAAE,MAAM,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,CAshFlE,CAAC;AAEF;;;GAGG;AACH,eAAO,MAAM,kBAAkB,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAiDrD,CAAC;AAEF,yCAAyC;AACzC,eAAO,MAAM,aAAa,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAuJhD,CAAC"}