normalizr 

Normalizes deeply nested JSON API responses according to a schema for Flux and Redux apps.

Installation

npm install simple-normalizr --save

The Problem

* You have a JSON API that returns deeply nested objects;
* You want to port your app to Flux or Redux;
* You noticed it's hard for Stores (or Reducers) to consume data from nested API responses.

Normalizr takes JSON and a schema and replaces nested entities with their IDs, gathering all entities in dictionaries.

For example,
##Assume SupportDesk scenario
* each contact create multiple ticket
* contact associate with one account
* ticket has conversation. conversation has multiple threads and multiple comments



``javascript
1. Denormalized Simple contact object
{
id:"c1",
name:"vimal"
}
2. Denormalized Array of Contact object
[
{
id:"c1",
name:"vimal1"
},
{
id:"c2",
name:"vimal2"
}
]
`

can be normalized to

1. Normalized Simple contact
`javascript
{
result: "c1",
entities: {
contacts: {
"c1": {
id: 1,
name:"vimal"
}
}
},
result:"c1"

}`

2. Normalized Array of Contact object
`javascript
{
entities:{
"contacts":{
"c1":{
id:"c1",
name:"vimal1"
},
"c2":{
id:"c2",
name:"vimal2"
}
}
},
result:["c1","c2"]
}
`

Note the flat structure (all nesting is gone).

Features

* Entities can be nested inside other entities, objects and arrays;
* Combine entity schemas to express any kind of API response;
* Entities with same IDs are automatically merged
* Allows using a custom ID attribute (e.g. slug).

Usage

`javascript
import { normalize, schema, arrayOf } from 'normalizr';
`

First, define a schema for our entities:
Simple Schema
`javascript
const schema = require('simple-normalizr').schema;
const contactSchema = schema('contacts');
`

Then we define nesting rules:

Nested Schema
`javascript
const schema = require('simple-normalizr').schema;
const accountSchema = schema("accounts");
const contactSchema = schema("contacts",{mapping:{ account:accountSchema } });
`

Now we can use this schema in our API response:

`javascript
const normalize = require('simple-normalizr').normalize;
const response={
id:"c1",
name:"vimal1",
account:{
id:"a1",
aname:"account1"
}
}
const normalizedContact = normalize(response, contact);

{
entities:{
"contacts":{
"c1":{
id:"c1",
name:"vimal1",
"account": "a1"
}
},
"accounts":{
"a1":{
id:"a1",
aname:"account1"
}
}
},
result:"c1"
}

`

API Reference

$3

Schema lets you define a type of entity returned by your API.
This should correspond to model in your server code.

The key parameter lets you specify the name of the dictionary for this kind of entity.

`javascript
const contact = schema('contacts');

// You can use a custom id attribute
const contact = schema('contacts',{ id: 'contact_id' });

assignEntity
function customAssignEntity(obj){
obj["newKey"]="newValue";
return obj
}
const normalizedContact = normalize(response,
schema("contacts",{ entityAssignment:customAssignEntity}))

{
entities:{
"contacts":{
"c1":{
"contact_id": "c1",
name:"vimal",
"newKey":"vimal"
}
}
},
result:"c1"
}

`
Lets you specify relationships between different entities.

`javascript
const account = schema('accounts');
const contact = schema('contacts',{mapping:{account:account}});

`

$3

Describes an array of the schema passed as argument.

`javascript
const arrayOf = require("simple-normalizr").arrayOf;
const ticket = schema('tickets');
const contact = schema('contacts',{mapping:{ticket:arrayOf(ticket)}});
`

If the array contains entities with different schemas

`javascript
const thread = schema("threads");
const comment = schema("comments");
const ticket = schema("ticket",
arrayOf(
schema({
union:{
thread:thread,
comment:comment
},
key:"type"
})))
`

$3

--Describes a map whose values follow the schema passed as argument.(not yet done)


--If the map contains entities with different schemas, (not yet done)

$3

Normalizes object according to schema.
Passed schema should be a nested object reflecting the structure of API response.

You may optionally specify any of the following options:

* assignEntity (function): This is useful if your backend emits additional fields, such as separate ID fields, you'd like to delete in the normalized entity. See the tests and the discussion for a usage example.

* mergeIntoEntity (not yet done) (function): You can use this to resolve conflicts when merging entities with the same key. See the test and the discussion for a usage example.

Dependencies

* Some methods from lodash, such as isObject, isEqual and mapValues
* selectn

Browser Support

Modern browsers with ES5 environments are supported.
The minimal supported IE version is IE 9.

Running Tests

`
git clone https://github.com/vimalceg/normalizr.git
cd normalizr
npm install
npm test # run tests once
npm run test:watch # run test watcher
``

Credits

Normalizr was originally created by Dan Abramov