Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

json-to-table

Growmies15.9kISC4.2.1

Convert an array of Objects into a table format

json, table, convert

readme

IMPORTANT NOTE

See the CHANGELOG for explanation of v3 vs v4.

Install

npm install json-to-table

Info

json-to-table converts an array of Javascript objects into a table format.

The column headers are all the possible "leaves" of the javascript objects.

Usage

const jsonToTable = require('json-to-table');

const myRecords = [
{
    name:'Bob',
    address:{zip:12345, state:'Euphoria'}
},
{
    name:'Jon',
    address:{street:'1234 Main St.', state:'Arizona'}
}];
const tabled = jsonToTable(myRecords);

//tabled will be an array of arrays like this
//[
//['name', 'address.zip', 'address.state', 'address.street'],
//['Bob',  12345,         'Euphoria',      ''],
//['Jon',  '',            '1234 Main St.', 'Arizona']
//]

Options

Some available options to pass in as the second argument are as follows.
Look at the tests to see all of these options in action.

{
  defaultValue: put whatever you want here //defaults to an empty string
  includeCollectionLength: if there is a subarray within the object, it will create a header and include that length //defaults to false
  excludeSubArrays: if there is a subarray within the object, it will remove it completely from the resulting table. //defaults to false
  checkKeyBeforePath: this will check for a key that has a '.' in it before assuming the '.' means to look deeper in the object //defaults to false
  listSubArrays: if there is a subarray that does not contain objects, it will list the full array instead of breaking it up into individual columns. //defaults to false
  stringifyObjects: stringify arrays and objects instead of breaking them up into individual columns // defaults to false
}

Notes

If a particular object did not have a key that another one did, the default will be an empty string. You can change the default value by passing an option in as the second parameter of the function call. If you explicitly pass undefined in as the second value, your defaults will be undefined.

const jsonToTable = require('json-to-table');

const myRecords = [
{
    name:'Bob',
    address:{zip:12345, state:'Euphoria'}
},
{
    name:'Jon',
    address:{street:'1234 Main St.', state:'Arizona'}
}];
const tabled = jsonToTable(myRecords, 'MY_DEFAULT_STR!!');

//tabled will be an array of arrays like this
//[
//['name', 'address.zip',     'address.state', 'address.street'],
//['Bob',  12345,             'Euphoria',      'MY_DEFAULT_STR!!'],
//['Jon',  'MY_DEFAULT_STR!!','Arizona',       '1234 Main St.']
//]

Also note that in this example, the address.zip was a number, and stayed a number.

License (ISC)

Copyright (c) 2015, Scott Hillman hillmanov@gmail.com

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

changelog

v4

We decided as a company that the fixes introduced in v3 are not going to be used in our app, and as a way to ensure we don't use those changes, we are reverting that portion of the code, and bumping up to v4. If the bugfix found in v3 is important to you, you'll have to use v3 explicitly, but please be aware WE WILL NOT be backporting future bugfixes/feature to v3. We are sorry if this creates any issues for you. If you have suggestions for a more robust solution, please open up a Github Issue and let us know!

v4.0.0

Undo the code change made in v3, but only tweak the tests to make sure we keep that unexpected behaviour in the future.

We also started using es6 code here in v4, so be aware.

v3

We bumped to v3 here because by fixing this bug, we potentially introduced a lot of broken metrics in the main app we are using this module for.

v3.0.0

Fixed a bug where arrays weren't playing nice when the exludeSubArrays option was true, AND when one of the arrays was null (ie. it was a leaf). That was causing an issue since one of the arrays was a leaf, then it was a valid path to data. So when creating the table, it would include a column at that point, and so the cells where the array wasn't null were being included as whole arrays. This seemed wrong especially since exludeSubArrays was set to true.

See these tests more easily visualize the issue

  • Should handle when a nested array has data for 1 object, but is null (which means is a leaf) in another object
  • Should handle when a nested array has data for 1 object, but is a primitive (which means is a leaf) in another object

v2

v2.1.5

Fixed an edge case with checkKeyBeforePath where the actual name of the key was something like ".ba`d"