Choice selections not being sent in on form submit, radio works

[aseem-md]

Hi All,

I have been trying to figure out what is happening here and have not quiet been able to figure out what is going on? I have a JSOField in a model, have a schema, in which there is a field for gender which is specified as:

"gender": { "type": "string", "choices": ["M", "F", "O"], },

What I noticed was that when the form gets saved,

• any changes I make to this field just gets ignored and the old value is being submitted.
• An array of items each of which is a choice it works fine and the updated list is submitted.
• If I use the radio widget the new value is submitted. (This is only tenable for small lists, I would like to use choice without radio buttons for larger choices list)

Perhaps I am missing something in the schema definition that would allow this to work?

Any help would be appreciated.

Thanks.

[bhch]

Could you give me a sample schema to reproduce it?

[aseem-md]

I will try to get a repo to you eod. Also I should mention that this is inside django-admin if that makes any difference. And if I cannot reproduce on a smaller scale, I will have to go spelunking. Thanks.

[aseem-md]

Apparently the minimum reduction case for django-admin works :/ Might have to debug form submission.

[aseem-md]

Hi,

So I created a reproduction case and was not able to reproduce data from the form not being submitted properly.

However this still seems to happen on the main app that I have. The differences I noticed were that in the repro case that the fields submitted were the rjf.. ones and a correct, updated jsonfield value.

The initial smaller image attached shows this.

However when I use the same code structure in my project, I get the rjf... variables that have the correct updated values, the builder variable that does not have the correct updated value and there is an additional field called initial-builder which does not show up in the repro case.

Perhaps I am missing something very basic related to how forms get processed?

Any help would be greatly appreciated.

[aseem-md]

Yes, that was specifically for debugging this. poetry based so you should be able to build and run it as is.

However I have not been able to reproduce the issue I am seeing in my code base although they are both doing exactly the same thing. For whatever reason the field named builder (in the second screenshot) does not contain the updated data, just the old data. In the attempted repro, modifying the the form, does submit the updated data in the bld field.

The attempted repro case also does not contain the initial-data field which is concerning, but it seems to work. Unfortunately I don't have a path forward to debug this as yet.

Thanks.

[aseem-md]

Happy to share my json schema via alternative means if that helps.

[aseem-md]

FYI On further investigation, in my schema, choices that are part of an array seem to work fine, however standalone choices do not get submitted to the POST.

[aseem-md]

Another FYI for the string enum drop downs if I convert them to an array type it seems to submit the right thing and I can transform it back and forth. I am not sure how I can reproduce it, but I will try and keep you posted.

[bhch]

I tried the sample repo. I'm unable to reproduce the behaviour and things are working as expected.

Happy to share my json schema via alternative means if that helps.

If it can help reproducing the bug, you can mail it to me. My email is mentioned on my profile page.