-
Notifications
You must be signed in to change notification settings - Fork 58
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
Field in CSV it turned into an object unexpectedly. #254
Comments
Hi @hydrohiester, thanks for reporting this. That definitely sounds like a bug to me. My guess is the parsing logic needs an update to account for that possibility, since it's completely valid. I'm currently traveling with no access to my typical development machine, but should hopefully be able to take a closer look at this either later this weekend or early next week. I'll keep you posted. |
Example: setPath({}, 'Account No.', '01'); /** results in: { 'Account No': { '': '01-1800-00' } } */ However, the '' key in the sub-doc should not be generated. Identified from report in mrodrig/json-2-csv#254 Fixes #39
Resolve #254 by updating doc-path to patched version
Thanks again for reporting this @hydrohiester. It ended up being a different issue with the logic in my |
Background Information
5.5.0
20.10.0
The issue I'm reporting is with:
I have...
Expected Behavior
CSV Header: 'Account No.'
CSV Field: '01-1800-00'
I expect to get:
{'Account No.': '01-1800-00'}
Actual Behavior
It gets converted to
{ 'Account No': { '': '01-1800-00' }}
If I remove the period in "Account No." it works correctly. Is a period not allowed in a heading?
I tried setting
excelBOM
to true, but it didn't make a difference.The text was updated successfully, but these errors were encountered: