Closed jgunstone closed 6 months ago
feels like a weird jupyter related bug so I just tried with jupyterlab=4.2 https://github.com/jupyterlab/jupyterlab/issues/15801
and it worked!
looks like that is slated for this week so I'll just hang tight until its out and try again
just tried with the jupyterlab==4.2
and unfortunately I'm getting the same original error
if I make the col names strings not numbers the bad behaviour stops, i.e.
it seems as though on the JS side of ipydatagrid
(or in lumino?) the integer col names are being coerced to strings and an additional column is added.
looking through the js side of things:
it appears from the above that there is a requirement to use a string for the name (though this wasn't previously enforced). FYI the referenced frictionless schema spec doesn't explicitly require the column name to be a string.
Does ipydatagrid require the pandas DataFrame to have string col names? should it?
... as unwanted column created with string name matching the integer on
set_cell_value
I'm just trying to update
ipyautoui
toipydatagrid>1.3.1
and came across this tricky little issue:Describe the bug
a new column with the string name of the edited column is created. This only happens when retrieving the data in a new cell.
To Reproduce
Expected behavior Behaves as expected for non-integer column names
Environment (please complete the following information):
@martinRenou - maybe you could help?