You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CSVs exported from Excel normally contain a byte-order-marker at the beginning of the file. It manifests as the first column header having invisible characters at the start of it, which will mean that it'll look like "handle" in your console but won't actually be equal to "handle" due to the invisible characters.
This issue has been automatically marked as stale because it has not had recent activity. It might be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It might be closed if no further activity occurs. Thank you for your contributions.
CSVs exported from Excel normally contain a byte-order-marker at the beginning of the file. It manifests as the first column header having invisible characters at the start of it, which will mean that it'll look like
"handle"
in your console but won't actually be equal to"handle"
due to the invisible characters.There's some info on the issue here: https://estl.tech/of-ruby-and-hidden-csv-characters-ef482c679b35
It's kind of annoying to tell clients to open their CSVs in Numbers.app or Google Sheets and export them from there.
The text was updated successfully, but these errors were encountered: