-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed field name editing #566
Conversation
Deploying opendataeditor with Cloudflare Pages
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job, @roll , it works now but shouldn't this change include also updating the name of the column to reflect the empty column name? with this fix now an error shows but the column name looks the same in the tabular representation, so it's kinda hard to see what is the error:
Hi @roll and @guergana! I tested this PR. The implementation works. In this sense, the ODE does not crash when changing the column name. However, if I go to the metadata panel, Schema--Fields and change the name of the column, the info is not updated. Should I create a separate issue for this @roll so we can merge this PR? Video showing the problem: Grabacion.de.pantalla.2024-09-27.a.la.s.2.53.11.p.m.mov |
@romicolman Yes, let's create a separate issue because current behaviour is correct regarding the initial concept of how data and metadata editing co-exist. In this case:
Probably we need to change it concept. Also I created this issue - #571 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! ✔️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New issue created :) #574
Thanks! |
Please make sure that all the checks pass. Please add here any additional information regarding this pull request. It's highly recommended that you link this PR to an issue (please create one if it doesn't exist for this PR)