Closed stevendesu closed 5 years ago
I may actually be experiencing two bugs. In my VueJS project I was receiving:
[
...
{id: 4, apop: "atl", zpop: "dal", speed: 200000, name: null, "lat": null, "lng": null, "type": null, "name_2": null, "lat_2": null, "lng_2": null, "type_2": null}
...
This led me to create this issue and a test case. However in the test case the merge was a lot more effective, only getting a single type field wrong.
I'm not sure if these are two manifestations of the same bug, or two separate bugs.
Upon further research, I had mistyped my expected.json
. The issue described does not repro using these CSVs and the code in this ticket.
I will have to do further investigation to figure out why the issue arises in my VueJS application.
I can't repro this even on my VueJS app. I'm going to guess I was having trouble with browser cache, my build tool, or some other step in the pipeline. This library works fine.
CSV1:
CSV2:
JavaScript:
Expected:
Actual:
The
type_2
field is incorrectAs this is real-world data that didn't work, let's do proper TDD and build a test case using this exact data.