-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
CSV importer: confusing behaviour of checkboxes #4299
Comments
I think both of the options should be connected as when the user is trying to enter the column names himself , then the parse next checkbox should be turned off . |
I absolutely love it! |
Maybe the Use character could be moved above the Trim ? |
@rachittiwari8562 The visual separation is optional and we don't have that in the other import loaders so I would remove those vertical section separators here in the CSV importer for now. Then I think we can merge. There are many many things that visually I would like to see changed and restyled throughout OpenRefine, but first we need a comprehensive plan and that will likely come after or along with OpenRefine 4.0 in phases. |
Got it... |
In the configuration options for the CSV/TSV importer, two checkboxes are linked as if one of them had to be checked.
This is a bad pattern: if those checkboxes are really meant to be grouped, then they should be radio buttons and be positioned next to each other.
To Reproduce
Steps to reproduce the behavior:
Current Results
Expected Behavior
In this case I was actually trying to get both checkboxes to be not checked (so that my project gets created with
Column 1
,Column 2
… as column headers). I can achieve this by keeping theParse next…
checkbox on and setting the number of lines to 0 but that is a bit counter-intuitive.Versions
The text was updated successfully, but these errors were encountered: