2.3.0 • Published 12 months ago

jsonapi-ts-deserializer v2.3.0

Weekly downloads
-
License
MIT
Repository
github
Last release
12 months ago

JSON:API deserializer in Typescript

cov

A JSON:API response payload is a normalized set of entities and their relationships plus some metadata. This package deserializes a JSON:API response payload into an object graph, using user-defined entity deserializers to build the actual entities.

Installation

npm i jsonapi-ts-deserializer

Usage

import { getDeserializer, ItemDeserializer, RelationshipDeserializer } from 'jsonapi-ts-deserializer';

// Introduce types for your entities, the folder:
type Folder = {
    id: number;
    name: string;
    children: (Folder | File)[];
}

// and the file:
type File = {
    id: number;
    name: string;
}

// Create a deserializer for the folder:
const folderDeserializer : ItemDeserializer<Folder> = {
    type: 'folders',
    deserialize: (item: Item, relationshipDeserializer: RelationshipDeserializer): Folder => {
        const folder: Folder = {
            id: parseInt(item.id),
            name: item.attributes.name,
            children: [],
        };

        folder.children = relationshipDeserializer.deserializeRelationships(relationshipDeserializer, item, 'children');

        return folder;
    },
}

// ...and also for the file:
const fileDeserializer: ItemDeserializer<File> = {
    type: 'files',
    deserialize: (item: Item, relationshipDeserializer: RelationshipDeserializer): File => {
        return {
            id: parseInt(item.id),
            name: item.attributes.name,
        };
    }
}

// create the deserializer with the folder and file deserializers registered:
const deserializer = getDeserializer([
    folderDeserializer,
    fileDeserializer,
]);

// Fetch your JSON:API data:
const yourJsonData = fetch('https://api.example.com/api/folders');

// consume it and get the root items with the complete object-graph:
const rootItems: any[] = deserializer.consume(yourJsonData).getRootItems();

Please note that the deserializer only supports successful responses, and you will get an error if the response is not compatible with the JSON:API specification. I practise the response should be checked for errors before deserializing it and the error handling should be done separately.

Examples

TODO

At least the following things are in the backlog:

  • Ditch the classes in the entity deserializers and use types instead
  • Consider caching the deserialized entities and reusing them
  • Come up with a spectacular logo for this package

Credits

Setting up the npm-package with all the bells and whistles would've taken me hours, so I followed the following tutorial for that part:

https://itnext.io/step-by-step-building-and-publishing-an-npm-typescript-package-44fe7164964c

2.3.0

12 months ago

2.2.0

12 months ago

2.1.0

12 months ago

2.0.1

1 year ago

2.0.0

1 year ago

1.1.3

1 year ago

1.1.2

1 year ago

1.1.1

1 year ago

1.1.0

1 year ago

1.0.1

1 year ago

1.0.0

1 year ago