Skip to content

fix: Enable Required toggle and default values for nested object properties#7532

Open
devdattatalele wants to merge 1 commit intowindmill-labs:mainfrom
devdattatalele:fix/issue-7476-nested-property-required
Open

fix: Enable Required toggle and default values for nested object properties#7532
devdattatalele wants to merge 1 commit intowindmill-labs:mainfrom
devdattatalele:fix/issue-7476-nested-property-required

Conversation

@devdattatalele
Copy link
Contributor

@devdattatalele devdattatalele commented Jan 9, 2026

Fixes #7476

This change enables the Required toggle and default value editor for nested object properties in script parameters. The issue was that EditableSchemaDrawer component lacked the isFlowInput and isAppInput props, which prevented FlowPropertyEditor from being rendered for nested properties.

The fix propagates these flags through EditableSchemaDrawer, PropertyEditor, and FlowPropertyEditor components. This ensures that when users edit nested object properties in the advanced UI settings, they can now set fields as required, configure default values, and use the nullable option to prevent auto-population of empty strings or arrays.

The changes are minimal and focused on prop propagation, maintaining backward compatibility while enabling full editing capabilities for nested properties.

…erties (windmill-labs#7476)

This fix propagates isFlowInput/isAppInput flags through EditableSchemaDrawer, PropertyEditor, and FlowPropertyEditor components to enable the Required toggle and default value editor for nested object properties in script parameters. The changes ensure that nested property settings persist correctly and are fully editable in the advanced UI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: Not able to set nested property of an object and array to required or provide default value

1 participant