Saw this question before but no solution. But there seems to be demand.
My usecase (simplified):
I pull a table from a database into a data editor. Columns ID (Primary Key), NAME (Alternate Key), DISPLAY_NAME.
The data_editor num_rows is st to “dynamic”.
I set the NAME column in the data editor to disabled=True because nobody should update the alternate key once it is created. Some other systems may depend on it.
But when creating a new row in the data_editor I have to enter it. This is blocked by the disabled=True flag
Would the following suggestion for a column_config implementation make sense?
if disabled == True and required == True → Let the user edit the cell.
If disabled == True and required == False → Block the user from editing the cell
or turned the other way around:
if disabled == False or required == True → Let the user edit the cell