npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@yamamotok/dataobject

v1.2.0

Published

Decorator based JSON serializer and deserializer.

Downloads

42

Readme

DataObject

codecov npm version

Main features

  • Transformation from a Class instance to a plain JavaScript object. (Serialization)
  • Transformation from plain a JavaScript object to a Class instance. (Deserialization)
  • Designed for TypeScript project, using TypeScript decorators.

Key concept

  • DataObject always takes whitelist approach. It means that;
    • Only @property decorated property will be output (serialized) into plain JavaScript object.
    • Only @property decorated property will be taken (deserialized) into class instance.

Limitation

  • Currently, Class inheritance is not supported.

Quick examples

class User {
  @property()
  @required()
  userId!: string;

  @property()
  name: string = '';

  @property()
  postalAddress?: Address;

  @property()
  @context('factory', 'toPlain')
  metadata: Record<string, unknown> = {};

  @property()
  tags: Set<string> = new Set();

  static factory = createFactory(User);
  static toPlain = createToPlain(User);
}

class Address {
  @property()
  @required()
  country!: string;

  @property()
  @required()
  @context('!public')
  @validator(isPostalCode)
  postalCode!: string;

  static factory = createFactory(Address);
  static toPlain = createToPlain(Address);
}

function isPostalCode(code: string) {
  return /^[\d]{7}$/.test(code);
}

const source = {
  userId: 'e7cebd38-9e3a-4487-9485-b3e3be03cd32',
  name: 'test user',
  postalAddress: {
    country: 'jp',
    postalCode: '1234567',
  },
  metadata: {
    lastLogin: 1622940893174,
  },
  tags: ['loyal', 'active'],
};

// Transformation from plain object to class instance. (deserialization)
const created = User.factory(source);

// Transformation from class instance to plain object. (serialization)
const plain = User.toPlain(created, 'public');

Decorators

@property decorator & "toPlain" and "factory" static methods

To enable a Class to work as "DataObject", you should do first;

  • Implement at least one @property decorated property.
  • Implement factory static method by using createFactory utility.
  • Implement toPlain static method by using createToPlain utility.

The simplest class looks like;

class Entity {
  @property()
  id?: string;

  static factory = createFactory(Entity);
  static toPlain = createToPlain(Entity); 
}

Value transformation for each types

DataObject will look up at types given through TypeScript type system for transformation. It is also possible to tell its type explicitly. Also, you can set your own transformer.

string, number, boolean (primitives)

@property
name: string;
  • In toPlain, value will be output as-is.
  • In factory, input value will be type-coerced.
@property
code: number;
  • In toPlain, value will be output as-is.
  • In factory, input value will be type-coerced. If the result is NaN, Error will be thrown.
@property
active: boolean;
  • In toPlain, value will be output as-is.
  • In factory, input value will be type-coerced.

Custom class

@property
active: CustomClass; // CustomClass is a "DataObject" which has factory and toPlain static methods.
  • In toPlain, value will be transformed with using CustomClass#toPlain().
  • In factory, value will be transformed with using CustomClass#factory().

array and Set

@property
list: string[];
  • In toPlain, each value in array will be output as-is.
  • In factory, each value in array will be taken as-is. (no type coercion)
  • Other types are same.
@property({ type: () => CustomClass })
list: CustomClass[];
  • Need to set type option to @property decorator.
  • In toPlain, each value in array will be transformed with using CustomClass#toPlain(). A special attribute __type: CustomClass will be added.
  • In factory, each value in array will be transformed with using CustomClass#factory().
@property({ type: () => [CustomClass, AnotherCustomClass] })
list: Array<CustomClass | AnotherCustomClass>; // Union type also works
  • Need to set type option to @property decorator.
  • In toPlain, each value in array will be transformed with using CustomClass#toPlain() or AnotherCustomClass#toPlain(). A special attribute __type: CustomClass or __type: AnotherCustomClass will be added.
  • In factory, each value in array will be transformed with using CustomClass#factory() or AnotherCustomClass#factory() according to a special attribute __type.
@property()
list: Set<string>;

@property({ type: () => CustomClass })
list: Set<CustomClass>;
  • Same as array

object and Map

@property
dict: Record<string, string>;
  • In toPlain, each value in object will be output as-is.
  • In factory, each value in object will be taken as-is. (no type coercion)
  • Other type pairs (e.g. Record<string, unknown>) are same.
@property{ type: () => CustomClass }
dict: Map<string, CustomClass>;
  • Need to set type options to @property decorator.
  • In toPlain, each value in array will be transformed with using CustomClass#toPlain(). A special attribute __type: CustomClass will be added.
  • In factory, each value in array will be transformed with using CustomClass#factory().
@property{ type: () => CustomClass, isMap: true }
dict: Record<string, CustomClass>;
  • Need to set type and isMap options to @property decorator if you want to use object like ES6 Map.
  • In toPlain, each value in array will be transformed with using CustomClass#toPlain(). A special attribute __type: CustomClass will be added.
  • In factory, each value in array will be transformed with using CustomClass#factory().
@property{ type: () => [CustomClass, AnotherCustomClass] }
dict: Map<string, CustomClass | AnotherCustomClass>;
  • Union type works same as array of union types.

undefined

  • If the value given to factory was undefined, the value is not taken in.

Custom transformation

You can use your own transformer by setting transformer option.

  @property({ transformer: jsDateTransformer })
  timestamp: Date = new Date();

Please check src/bundle/jsDateTransformer for actual transformer implementation, which transformed JavaScript Date object to ISO date string and vice-versa.

@required

In case a property has been decorated with @required, factory will check if the property really exists in given source.

  @property()
  @required()
  id!: string;

Error will be thrown if it is missing.

@context

You can make transformation work only in specific contexts.

  • factory method has "factory" context as default.
  • toPlain method has "toPlain" context as default.
class Entity {
  @property()
  @context('!response')
  id: string;
  
  @property('response')
  get name(): string { ... }
}

Entity.toPlain(instance, 'response');

You can specify custom context to both toPlain and factory. Exclusion (heading !) is available. With above example, toPlain will output only name into resulted object.

@spread

You can spread the value in toPlain process with using @spread decorator. Also, you can give context option which works same as @context.

class Entity {
  @property()
  id: string = 'my-id'

  @property
  @spread
  details?: Record<string, unknown> = { item: 'value' }
}

Entity.toPlain(instance);

With above example, details is spread, and the result should look like;

{ id: "my-id", item: "value" }

@validator

You can set validator function which is invoked in 'factory'.

Validator function should return true or nothing (undefined) in case of success.
In case of failure, it should return false or Error, or should throw Error.

If some validation failed, 'factory' will throw ValidationError. You can check what properties failed by checking the error thrown.

class Entity {
  @property()
  @validator((v: string) => v.length <= 4)
  id?: string;

  static factory = createFactory(Entity);
  static toPlain = createToPlain(Entity);
}
try {
  const entity = Entity.factory({ id: 'a_little_too_long' });
} catch (err) {
  // err should be instance of ValidationError
  // err.causes[0].key should be 'id'
  // err.causes[0].error should be 'id validation failed'
}

Be noted the validator will be applied after value transformation finished, that means the argument validator takes is already transformed value.

License (MIT)

Copyright (c) 2021 Keisuke Yamamoto