Allow for accessing nested object data.

[GrandVizierOlaf]

This PR allows for the use of dot notation in the column names to access nested object data.

For instance, the modified example adds a phone object to each existing user and each phone has a "home" and "cell" attribute. These nested attributes can be accessed with a column name of "phone.home" and "phone.cell", respectively.

Any amount of nested will work with this.

This addresses #147, #531, and (I think) #475.

[coveralls]

Coverage decreased (-0.1%) to 76.997% when pulling 58f2799 on GrandVizierOlaf:master into dc45413 on gregnb:master.

[skyleronken]

Can we merge this? the conflict is in the package-lock.json file and those changes are only on optional flags.

[gabrielliwerant]

We can't merge this until the conflicts are resolved, but it also needs review, which I will provide when I have the time.

[gabrielliwerant]

This is really nice, and looks like a highly requested feature.

I think we just need to clean up the edge case where we have improper/missing paths.

[gabrielliwerant]

Also would be great to have a test for this, if you've got the time.

[gabrielliwerant]

Thank you for adding the undefined check! I will attempt a test before next release, but this looks good for merge.

[empav]

Hey guys, is this feature working? I've the following issue:

const applicant = { name: 'test', surname: 'test' };

[gabrielliwerant]

@epavan I need more information to debug your code (in particular, the actual code). Make sure you are using this feature as indicated in the example data-as-object.