Unable to Reset Form for Object-Type Fields in JSON Schema-Based Form
I am creating a form using a JSON schema with the following structure:
{
"properties": {
"payload": {
"type": "object",
"description": "The base payload structure required to trigger the agent. This is a JSON object.",
"title": "Agent Payload"
},
"inputFieldName": {
"type": "string",
"description": "The key to add dynamically to the payload structure. The value for this key will be input through the chat interface.",
"title": "Additional Field Name",
"placeholder": "Enter the key to include in the payload (e.g., input)"
}
},
"required": ["payload", "inputFieldName"]
}
When I reset the form, the input field for the string type (inputFieldName) resets successfully, but the UI does not reset for the object type (payload). While I can see that the value of the payload field is being cleared programmatically, this change is not reflected in the UI. It appears that the component's internal state is not updating properly for object-type fields.
Has anyone faced a similar issue, or could someone guide me on how to ensure the UI reflects the reset action for object-type fields?
8 Replies
Hi Deepak, we solved a similar issue very recently, are you on the latest release
I'm currently using v1.441
could you try with a newer release when you have time or on app.windmill.dev
Hi @rubenf
I've tested this on app.windmill.dev as per your suggestion. Unfortunately, the issue persists. There is no visible change in the UI for the object type fields, whether it's for value updates or form resets. The changes are reflected in the component's value but not in the UI.
Please let me know if there's anything else you'd like me to check or test further.
Thanks
I will try it out now
yeah I can reproduce, I will be on it
you're from endowus correct?
No @rubenf
Hi @rubenf
Any update on this?
At the moment not, I thought you were an EE customer but it doesn't seem to be the case so we assigned the issue a normal priority. We will do some improvements in the coming weeks that will results in the issue being fixed as a side-effect
Okay, Thanks @rubenf