angular-user-friendly-json-tree

Angular directive for displaying, in a user friendly way, a JSON object in an expandable tree structure


Keywords
angular, json
License
CC-BY-4.0
Install
bower install angular-user-friendly-json-tree

Documentation

Angular User Friendly JSON Tree

This plugin allows an easily way to visualize JSON/JS Object trees, in a user friendly manner. From a development standpoint, when querying API endpoints and wishing to easily visualize the response object—or when looking for an easy way to display a complex object— this plugin provides an easy to use directive for displaying, in a user friendly way, the Object tree response.

This is nice and easy because all you should have to do is include the directive in your app, and then pass a reference to the directive of which object on the scope you want it to display.

The user friendly display of the Json/JS object tree works by formatting the tree's nodes names from camel cased to uncamel cased names; it also provides a user friendly way to visualize nodes with dates in milliseconds and empty nodes.

A live implementation of this directive can be found at http://blog.alexwendland.com/angular-json-tree/ and the source for that project can be found on the gh-pages branch.

Requirements: AngularJS 1.2+

File Size: v2.0.0

  • JS: 9Kb raw, 3Kb minified, 953b gzipped
  • JS + CSS: 11Kb raw, 4.3Kb minified, 1.489b gzipped

Usage:

  1. Include user-friendly-angular-json-tree as a dependency for your app
angular.module('myApp', ['user-friendly-angular-json-tree'])
  1. Include the supplied CSS file (or create your own).
  2. Setup the directive and reference a json tree and options objects on your scope

JavaScript:

$scope.someobj = {
    test: 'hello',
    someArray: [1, 2, 3, 4, 5, 6],
    subObj: {
    subTest: 'hi',
    subArray: [2, 1, 3, 4, 7, 11]
    },
    withDate: 1505296820331,
    emptyVal: ''
};

HTML:

<user-friendly-json-tree object="someobj"></user-friendly-json-tree>

via bower:

$ bower install user-friendly-angular-json-tree

Why I created this:

I was searching for a way to easily display,in a user friendly way, the JSON results from an API endpoint. The objects were dynamic and followed no uniform pattern. Thus I created this AngularJS directive. Given the above input (from Usage), you can see below, on the right, the final result produced by this directive:

Example Output

This directive helps me with another problem while developing: visualizing JSON objects in a user friendly way. Being able to break down JSON objects piece by piece has proven invaluably useful. To simplify that process, I threw together this website: http://blog.alexwendland.com/angular-json-tree/.

Directive Configuration:

These attributes are available for configuration on the directive:

object [required]

The object property takes the name of an object on the $scope. This object will be displayed as an expandable tree.

<user-friendly-json-tree object="someobj"></user-friendly-json-tree>

options

The object property takes the name of an options object on the $scope. This object allows the following customizations:

  • expandable nodes (branches) label text (toggleBranchText option). Default value is "click to expand"
  • date format for leaf fields values of type Date (dateFormat option). The directive considers a leaf node to be of type Date, if the node's name ends with the word "Date" and its value is a date in milliseconds. The Default value of this options is the ISO 8601 format "yyyy-MM-dd HH:mm:ss"
  • a user friendly text to represent empty values of nodes (emptyValueText option). Default value is "none"
$scope.someOptions = {
    toggleBranchText: 'click to expand',
    emptyValueText: 'none',
    dateFormat: 'yyyy-MM-dd HH:mm:ss'
};
<user-friendly-json-tree object="someobj" options="someOptions"></user-friendly-json-tree>

start-expanded [optional, default=false]

This is an optional attribute that designates if the tree's root should display as expanded initially. This is useful when you are only showing one json-tree, but would probably be set to false if json-trees were being created with an ng-repeat loop.

<user-friendly-json-tree object="someobj" start-expanded="true"></user-friendly-json-tree>

root-name [optional, default='Object']

This is an optional attribute that sets the title displayed at the root node. This is useful when you are showing sub-portions of an object or want the object root node to have a different string than 'Object'.

<user-friendly-json-tree object="someobj" root-name="'Name'"></user-friendly-json-tree>

Styling

The default CSS is separated into two parts: structure and looks. The looks section can be easily modified in order to change font, color and toggle buttons. The structure section can also be modified, but some more care will be needed because it provides the framework from which this directive provides functionality. The looks framework will be covered here while the structure framework will only be touched on.

The user-friendly-json-tree is based on recursive nodes of two basic structures. The first structure is for nodes that have no subnodes themselves (a leaf), and the other is for nodes that have children (a branch). Here the simplified template structures for each, with appropriate, style-able, class names.

Leaf Nodes

<user-friendly-json-node class="not-expandable">
    <span class="key">{{key}}</span>
    <span class="leaf-value">{{value}}</span>
</user-friendly-json-node>

In the default CSS, all .key elements have the same style, a bold blue color. There is some padding, and then the property's value follows. By default, no special styling is applied to .lead-value elements.

Branch Nodes

Branch nodes have two states: expanded or not-expanded. The not-expanded state is very similar to the leaf nodes and simply exchanges the .leaf-value class for .branch-preview.

<user-friendly-json-node class="not-expandable">
    <span class="key">{{key}}</span>
    <span class="branch-preview">{{value}}</span>
</user-friendly-json-node>

In the default CSS, .branch-preview elements are italicized, concatenated, hidden overflow, and reduced in opacity.

The expanded state is different and contains further subnodes that are generated with ng-repeat:

<user-friendly-json-node class="expandable">
    <span class="key">{{key}}</span>
    <ul class="branch-value">
        <li ng-repeat>
            <user-friendly-json-node>{{subnode values}}</user-friendly-json-node>
        </li>
    </ul>
</user-friendly-json-node>

The .expandable class adds several features to the normal user-friendly-json-node element. Particularly, by the default looks CSS, a carrot-style toggle pseudo-element will be created. This ::before element will rotate 90 deg downward when the element is expanded.

Additionally, user-friendly-json-node elements receive a class corresponding to their object type. For example, the .array class or .object may be placed on a user-friendly-json-node. These classes can be used for special stylings.

Further Explanation:

An example implementation of this project can be found at the gh-pages branch of this repository.

Changelog

v2.0.0

  • Changed npm and bower packages names
  • Changed JSON/JS Object tree visualization to be user friendly

v1.0.0

  • Update npm dev dependencies to latest (as of 2016-05-24) and remove unnecessary ones
  • Update angular dependency to accept all 1.x versions
  • Set main in bower.json and package.json properly so that this package can easily be included in bower and npm managed projects (Issue #7, PR #1)
  • Allow setting the name of the root node (Issue #5)
    • This can be done setting the root-name attribute on the directive. An evaluatable expression must be provided, such as root-name="'My name'".

v0.0.1

  • Initial release

Credits:

Thank you to Mark Lagendijk from StackOverflow for providing a service than assists in recursive directives. That post can be found here.

Also, thank you to chieffancypants for his angular-loading-bar project from which I used the README.md as inspiration for this (poor) one.

License:

Licensed under the Creative Commons Attribution 4.0 International (CC-BY-4.0)