Socket
Socket
Sign inDemoInstall

@loopback/metadata

Package Overview
Dependencies
3
Maintainers
17
Versions
163
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

Comparing version 0.8.7 to 0.8.8

8

CHANGELOG.md

@@ -6,2 +6,10 @@ # Change Log

<a name="0.8.8"></a>
## [0.8.8](https://github.com/strongloop/loopback-next/compare/@loopback/metadata@0.8.7...@loopback/metadata@0.8.8) (2018-06-20)
**Note:** Version bump only for package @loopback/metadata
<a name="0.8.7"></a>

@@ -8,0 +16,0 @@ ## [0.8.7](https://github.com/strongloop/loopback-next/compare/@loopback/metadata@0.8.5...@loopback/metadata@0.8.7) (2018-06-09)

8

package.json
{
"name": "@loopback/metadata",
"version": "0.8.7",
"version": "0.8.8",
"description": "LoopBack's metadata utilities for reflection and decoration",

@@ -30,5 +30,5 @@ "engines": {

"devDependencies": {
"@loopback/build": "^0.6.8",
"@loopback/dist-util": "^0.3.2",
"@loopback/testlab": "^0.10.7",
"@loopback/build": "^0.6.9",
"@loopback/dist-util": "^0.3.3",
"@loopback/testlab": "^0.10.8",
"@types/debug": "^0.0.30",

@@ -35,0 +35,0 @@ "@types/lodash": "^4.14.106",

@@ -202,4 +202,4 @@ # @loopback/metadata

1. Method decorators cannot be applied to a constructor
2. Method decorators depends on the positions to match parameters
1. Method decorators cannot be applied to a constructor
2. Method decorators depends on the positions to match parameters

@@ -224,8 +224,8 @@ We recommend that `ParameterDecorator` be used instead.

1. If the metadata is an object, we merge the `spec` argument from the
decorator function into the inherited value from base classes. For metadata
of array and other primitive types, the `spec` argument is used if provided.
1. If the metadata is an object, we merge the `spec` argument from the
decorator function into the inherited value from base classes. For metadata
of array and other primitive types, the `spec` argument is used if provided.
- We can override `inherit` method of the decorator factory to customize how
to resolve `spec` against the inherited metadata. For example:
- We can override `inherit` method of the decorator factory to customize how
to resolve `spec` against the inherited metadata. For example:

@@ -239,9 +239,9 @@ ```ts

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:
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)
- MyClass (the constructor function itself)

@@ -317,5 +317,5 @@ ```ts

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.
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.

@@ -426,4 +426,4 @@ ```ts

const CLASS_KEY = MetadataAccessor.create<MyClassMetadata, ClassDecorator>(
'my-class-decorator-key',
);
'my-class-decorator-key',
);

@@ -477,3 +477,4 @@ // Create a class decorator with the key

See [all contributors](https://github.com/strongloop/loopback-next/graphs/contributors).
See
[all contributors](https://github.com/strongloop/loopback-next/graphs/contributors).

@@ -480,0 +481,0 @@ ## License

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Packages

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc