appsmithorg / appsmith

Platform to build admin panels, internal tools, and dashboards. Integrates with 25+ databases and any API.
https://www.appsmith.com
Apache License 2.0
34.6k stars 3.73k forks source link

[Bug]: Cant't edit Array type values in JSON Form #30078

Open thebadking opened 10 months ago

thebadking commented 10 months ago

Is there an existing issue for this?

Description

Can't edit values on Array type

Steps To Reproduce

image

Public Sample App

No response

Environment

Production

Issue video log

No response

Version

Cloud

animeshMondal-crypto commented 10 months ago

can i work on this issue ??

pranavkanade commented 10 months ago

@thebadking can you please share a recording of the bug in action or a sample app that shows this issue?

thebadking commented 10 months ago

screen-capture.webm

Nikhil-Nandagopal commented 10 months ago

@thebadking we're not able to see the video. Could you attach a list of steps or a public forkable app?

thebadking commented 10 months ago

the video plays on the github platform on chrome for sure, here is a screenshot you see when i hover over the input field i get only a "draggable" hand

image
thebadking commented 10 months ago

The steps are very simple just add an Array type to a form and try to edit the fields

Nikhil-Nandagopal commented 10 months ago

@thebadking able to see the video now.

thebadking commented 10 months ago

image

Untitled application 1.json

with some more digging I relised the bug happens on the auto generated form fields when you change them to array type, if you create a custom field it works, so it definitely looks like a bug

thebadking commented 10 months ago

I attached the app.json but it is a new project using the default users data mockup

jacquesikot commented 1 month ago

@thebadking I have been able to replicate the error from the app json you provided.

The issue is in the Field configuration property of the gender array column. From the image below, you can see that field configuration has - No fields configured

Screenshot 2024-10-11 at 12 16 26 PM

On the custom field, it works because there are field configs for the column as seen below

Screenshot 2024-10-11 at 12 16 08 PM

Updating the field configuration from the Gender property pane will solve the problem.