fix(workflow-executor): coerce update-record value to field type, support boolean and arrays#1612
Conversation
…port boolean and arrays
|
Coverage Impact This PR will not change total coverage. Modified Files with Diff Coverage (1)
🛟 Help
|
| // User may override the AI-proposed value with any field type (boolean, array, etc.). | ||
| // The business type is validated/coerced field-aware in the update-record step executor | ||
| // (buildZodSchemaForField), so the HTTP schema stays a shape guard only — aligned with | ||
| // `actionResult` below. | ||
| value: z.unknown().optional(), |
There was a problem hiding this comment.
your frontend PR ensure only string or number is sent
There was a problem hiding this comment.
I'm ok to leave the executor more permissive, it will allow future changes more easily. But you can remove the coms
2 participants
PRD-408
Definition of Done
General
Security