Utilities to help developers implement TypeScript decorators, define/merge metadata, and inspect metadata
npm install @loopback/metadataThis module contains utilities to help developers implement
TypeScript decorators,
define/merge metadata, and inspect metadata.
- Reflector: Wrapper of
reflect-metadata
- Decorator factories: A set of factories for class/method/property/parameter
decorators to apply metadata to a given class and its static or instance
members.
- MetadataInspector: High level APIs to inspect a class and/or its members to
get metadata applied by decorators.
``ts
import {ClassDecoratorFactory} from '@loopback/metadata';
export interface MyClassMetadata {
name: string;
description?: string;
}
function myClassDecorator(spec: MyClassMetadata): ClassDecorator {
return ClassDecoratorFactory.createDecorator
'metadata-key-for-my-class-decorator',
spec,
{decoratorName: '@myClassDecorator'},
);
}
`
Alternatively, we can instantiate the factory and create a decorator:
`ts`
function myClassDecorator(spec: MyClassMetadata): ClassDecorator {
const factory = new ClassDecoratorFactory
'metadata-key-for-my-class-decorator',
spec,
);
return factory.create();
}
Now we can use @myClassDecorator to add metadata to a class as follows:
`ts`
@myClassDecorator({name: 'my-controller'})
class MyController {}
`ts
import {MethodDecoratorFactory} from '@loopback/metadata';
export interface MyMethodMetadata {
name: string;
description?: string;
}
function myMethodDecorator(spec: MyMethodMetadata): MethodDecorator {
return MethodDecoratorFactory.createDecorator
'metadata-key-for-my-method-decorator',
spec,
);
}
`
Now we can use @myMethodDecorator to add metadata to a method as follows:
`ts
class MyController {
@myMethodDecorator({name: 'my-method'})
myMethod(x: string): string {
return 'Hello, ' + x;
}
@myMethodDecorator({name: 'another-method'})
anotherMethod() {}
@myMethodDecorator({name: 'my-static-method'})
static myStaticMethod() {}
}
`
Instead of a single immutable object to be merged, the
MethodMultiDecoratorFactory reduced parameters into a flat array of items.
When fetching the metadata later, you will receive it as an array.
`ts
import {MethodMultiDecoratorFactory} from '@loopback/metadata';
function myMultiMethodDecorator(spec: object): MethodDecorator {
return MethodMultiDecoratorFactory.createDecorator
Now, you can use it multiple times on a method:
`ts
class MyController {
@myMultiMethodDecorator({x: 1})
@myMultiMethodDecorator({y: 2})
@myMultiMethodDecorator({z: 3})
public point() {}
}
class MyOtherController {
@myMultiMethodDecorator([{x: 1}, {y: 2}, {z: 3}])
public point() {}
}
`
And when you access this data:
`ts
const arrayOfSpecs = MetadataInspector.getMethodMetadata
// [{z: 3}, {y: 2}, {x: 1}]
`
Typescript
applies decorators in reverse order
per class, from the parent down. The metadata array returned by getOwnMetadata
will be in this order:
`ts
class Parent {
@myMultiMethodDecorator('A') // second
@myMultiMethodDecorator('B') // first
public greet() {}
}
class Child extends Parent {
@myMultiMethodDecorator(['C', 'D']) // [third, fourth]
public greet() {}
}
class Grandchild extends Child {
@myMultiMethodDecorator('E') // sixth
@myMultiMethodDecorator('F') // fifth
public greet() {}
}
// getMethodMetadata = ['B', 'A', 'C', 'D', 'F', 'E']
`
You can also create a decorator that takes an object that can contain an array:
`ts
interface Point {
x?: number;
y?: number;
z?: number;
}
interface GeometryMetadata {
points: Point[];
}
function geometry(...points: Point[]): MethodDecorator {
return MethodMultiDecoratorFactory.createDecorator
'metadata-key-for-my-method-multi-decorator',
points,
);
}
class MyGeoController {
@geometry({x: 1})
@geometry({x: 2}, {y: 3})
@geometry({z: 5})
public abstract() {}
}
const arrayOfSpecs = MetadataInspector.getMethodMetadata
'metadata-key-for-my-method-multi-decorator',
constructor.prototype,
op,
);
// [
// { points: [{x: 1}]},
// { points: [{x:2}, {y:3}]},
// { points: [{z: 5}]},
// ]
`
`ts
import {PropertyDecoratorFactory} from '@loopback/metadata';
export interface MyPropertyMetadata {
name: string;
description?: string;
}
function myPropertyDecorator(spec: MyPropertyMetadata): PropertyDecorator {
return PropertyDecoratorFactory.createDecorator
'metadata-key-for-my-property-decorator',
spec,
);
}
`
Now we can use @myPropertyDecorator to add metadata to a property as follows:
`ts
class MyController {
@myPropertyDecorator({name: 'my-property'})
myProperty: string;
@myPropertyDecorator({name: 'another-property'})
anotherProperty: boolean;
@myPropertyDecorator({name: 'my-static-property'})
static myStaticProperty: string;
}
`
`ts
import {ParameterDecoratorFactory} from '@loopback/metadata';
export interface MyParameterMetadata {
name: string;
description?: string;
}
function myParameterDecorator(spec: MyParameterMetadata): ParameterDecorator {
return ParameterDecoratorFactory.createDecorator
'metadata-key-for-my-parameter-decorator',
spec,
);
}
`
Now we can use @myParameterDecorator to add metadata to a parameter as
follows:
`ts
class MyController {
constructor(
@myParameterDecorator({name: 'logging-prefix'}) public prefix: string,
@myParameterDecorator({name: 'logging-level'}) public level: number,
) {}
myMethod(
@myParameterDecorator({name: 'x'}) x: number,
@myParameterDecorator({name: 'y'}) y: number,
) {}
static myStaticMethod(
@myParameterDecorator({name: 'a'}) a: string,
@myParameterDecorator({name: 'b'}) b: string,
) {}
}
`
`ts
import {MethodParameterDecoratorFactory} from '@loopback/metadata';
export interface MyParameterMetadata {
name: string;
description?: string;
}
function myMethodParameterDecorator(
spec: MyParameterMetadata,
): MethodDecorator {
return MethodParameterDecoratorFactory.createDecorator
'metadata-key-for-my-method-parameter-decorator',
spec,
);
}
`
Now we can use @myMethodParameterDecorator to add metadata to a parameter as
follows:
`ts`
class MyController {
@myMethodParameterDecorator({name: 'x'})
@myMethodParameterDecorator({name: 'y'})
myMethod(x: number, y: number) {}
}
WARNING: Using method decorators to provide metadata for parameters is
strongly discouraged for a few reasons:
1. Method decorators cannot be applied to a constructor
2. Method decorators depends on the positions to match parameters
We recommend that ParameterDecorator be used instead.
An object of type DecoratorOptions can be passed in to create decorator
functions. There are two flags for the options:
- allowInheritance: Controls if inherited metadata will be honored. Default to
true.spec
- cloneInputSpec: Controls if the value of argument will be cloned.template
Sometimes we use shared spec for the decoration, but the decorator function
might need to mutate the object. Cloning the input spec makes it safe to use
the same spec () to decorate different members. Default to true.@inject
- decoratorName: Name for the decorator such as for error and
debugging messages.
By default, the decorator factories allow inheritance with the following rules:
1. If the metadata is an object, we merge the spec argument from thespec
decorator function into the inherited value from base classes. For metadata
of array and other primitive types, the argument is used if provided.inherit
- We can override method of the decorator factory to customize howspec
to resolve against the inherited metadata. For example:
`ts`
protected inherit(inheritedMetadata: T | undefined | null): T {
// Ignore the inherited metadata
return this.spec;
}
2. Method/property/parameter level metadata is applied to the class or its
prototype as a map keyed method/property names. We think this approach is
better than keeping metadata at method/property level as it's not easy to
inspect a class to find static/instance methods and properties with
decorations. The metadata for a class is illustrated below:
- MyClass (the constructor function itself)
`ts`
{
// Class level metadata
'my-class-decorator-key': MyClassMetadata,
// Static method (including the constructor) parameter metadata
'my-static-parameter-decorator-key': {
'': [MyConstructorParameterMetadata], // Constructor parameter metadata
'myStaticMethod1': [MyStaticMethodParameterMetadata],
'myStaticMethod2': [MyStaticMethodParameterMetadata],
},
// Static method metadata
'my-static-method-decorator-key': {
'myStaticMethod1': MyStaticMethodMetadata,
'myStaticMethod2': MyStaticMethodMetadata,
},
// Static property metadata
'my-static-property-decorator-key': {
'myStaticMethod1': MyStaticPropertyMetadata,
'myStaticMethod1': MyStaticPropertyMetadata,
}
}
- MyClass.prototype
`ts`
{
// Instance method parameter metadata
'my-instance-parameter-decorator-key': {
'myMethod1': [MyMethodParameterMetadata],
'myMethod2': [MyMethodParameterMetadata],
},
// Instance method metadata
'my-instance-method-decorator-key': {
'myMethod1': MyMethodMetadata,
'myMethod2': MyMethodMetadata,
},
// Instance property metadata
'my-instance-property-decorator-key': {
'myProperty1': MyPropertyMetadata,
'myProperty2': MyPropertyMetadata,
}
}
The following methods in DecoratorFactory allow subclasses to customize how tospec
merge the with existing metadata for a class, methods, properties, andM
method parameters. Please note is a map for methods/properties/parameters.
`ts
protected mergeWithInherited(
inheritedMetadata: M,
target: Object,
member?: string,
descriptorOrIndex?: TypedPropertyDescriptor
): M {
// ...
}
protected mergeWithOwn(
ownMetadata: M,
target: Object,
member?: string,
descriptorOrIndex?: TypedPropertyDescriptor
): M {
// ...
}
`
3. The default implementation throws errors if the same decorator function is
applied to a given target member (class/method/property/parameter) more than
once. For example, the following usage will report an error at runtime.
`ts`
@myClassDecorator({name: 'my-controller'})
@myClassDecorator({name: 'your-controller'})
class MyController {}
MetadataInspector provides API to inspect metadata from a class and its
members.
`ts
import {MetadataInspector} from '@loopback/metadata';
const meta = MetadataInspector.getClassMetadata(
'my-class-decorator-key',
MyController,
);
`
`ts
import {MetadataInspector} from '@loopback/metadata';
const meta = MetadataInspector.getClassMetadata
'my-class-decorator-key',
MyController,
{
ownMetadataOnly: true,
},
);
`
`ts
import {MetadataInspector} from '@loopback/metadata';
const allMethods = MetadataInspector.getAllMethodMetaData
'my-method-decorator-key',
MyController.prototype, // Use MyController for static methods
);
const myMethod = MetadataInspector.getMethodMetaData
'my-method-decorator-key',
MyController.prototype, // Use MyController for static methods
'myMethod',
);
`
`ts
import {MetadataInspector} from '@loopback/metadata';
const allProps = MetadataInspector.getAllPropertyMetaData
'my-property-decorator-key',
MyController.prototype, // Use MyController for static properties
);
const myProp = MetadataInspector.getMethodMetaData
'my-property-decorator-key',
MyController.prototype, // Use MyController for static properties
'myProp',
);
`
`ts
import {MetadataInspector} from '@loopback/metadata';
const allParamsForMyMethod =
MetadataInspector.getAllParameterMetaData
'my-parameter-decorator-key',
MyController.prototype, // Use MyController for static methods,
'myMethod',
);
const firstParamForMyMethod =
MetadataInspector.getMyParameterMetaData
'my-parameter-decorator-key',
MyController.prototype, // Use MyController for static methods
'myMethod',
0, // parameter index
);
const allParamsForConstructor =
MetadataInspector.getAllParameterMetaData
'my-parameter-decorator-key',
MyController,
'',
);
`
You can use MetadataAccessor to provide type checks for metadata access via
keys. For example,
`ts
const CLASS_KEY = MetadataAccessor.create
'my-class-decorator-key',
);
// Create a class decorator with the key
const myClassDecorator = ClassDecoratorFactory.createDecorator(CLASS_KEY);
// Inspect a class with the key
const myClassMeta = MetadataInspector.getClassMetaData(CLASS_KEY, MyController);
`
Please note MetadataKey can be an instance of MetadataAccessor or a string.
`ts
import {MetadataInspector} from '@loopback/metadata';
const myPropType = MetadataInspector.getDesignTypeForProperty(
MyController.prototype,
'myProp',
);
const myConstructor = MetadataInspector.getDesignTypeForMethod(
MyController,
'',
);
const myMethod = MetadataInspector.getDesignTypeForMethod(
MyController.prototype, // Use MyController for static methods
'myMethod',
);
`
`sh`
npm install --save @loopback/metadata
Run npm test` from the root folder.
See
all contributors.
MIT