In the complex object example, what's the usecase for turning that nested object into a multi-column CSV? I guess the overarching question is, why turn a single object at all into a CSV? It's just as machine/human readable as the JSON version of it, and there's no particular benefit in using either structure as it's not data meant to be processed in bulk.
The complex array usecase is where an opinionated-type of conversion tool is particularly needed, but I wonder why it behaves like this:
name: 'Robert',
lastname: 'Miller',
family: null,
location: [1231,3214,4214]
Why not have `location_1, location_2, location_3`, instead of having a single location column? The latter implementation makes the data difficult to quickly use in a program (like a spreadsheet).