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

loopback-setup-hooks-mixins

v1.0.0

Published

Mixins for Loopback, to easily configure operation and remote hooks from the model configuration file.

Downloads

20

Readme

loopback-setup-hooks-mixins

Mixin for Loopback, to easily configure operation and remote hooks from the model configuration file.

It works with Loopback 2 and Loopback 3.

Installation

npm install --save loopback-setup-hooks-mixins

Configuration

First, modify your server/model-config.json to include the path to this module:

{
  "mixins": [
    "loopback/common/mixins",
    "loopback/server/mixins",
    "../common/mixins",
    "./mixins",
    "../node_modules/loopback-setup-hooks-mixins"
  ]
}

Then you can use the mixins from your model definition files:

...
  "mixins": {
    "SetupOperationHooks": {
      "source": "./common/models/employee-hooks.js",
      "before save": ["doSomething"],
      "before delete": ["checkSomething"]
    },
    "SetupRemoteHooks": {
      "source": "./common/models/employee-hooks.js",
      "beforeRemote": {
        "deleteById": ["checkSomethingElse"],
      },
      "afterRemote": {
        "create": ["doSomethingElse"]
      }
    }
  }
...

Available mixins

SetupOperationHooks

Configures the defined operation hooks in the model.

Options

  • source (optional)
  • name of the operation hooks (e.g. "before save", "after save", etc.)

Usage

For each operation hook that you want to configure, you will need to define a string or an array with the name(s) of the method(s) that should be called.

If you define source option, it will search the methods in that file, otherwise it will search the methods in the Model.

  "mixins": {
    "SetupOperationHooks": {
      "source": "./common/models/employee-hooks.js",
      "before save": "doSomething",
      "before delete": ["checkSomething", "doSomethingElse"]
    }
  }

The source file (employee-hooks.js in our example) would look like this:

const Promise = require('bluebird');

module.exports = {
  doSomething,
  checkSomething,
  doSomethingElse,
};

function doSomething(context) {
  return new Promise((resolve, reject) => {
    resolve();
  });
}

function checkSomething(context) {
  return new Promise((resolve, reject) => {
    resolve();
  });
}

function doSomethingElse(context) {
  return new Promise((resolve, reject) => {
    resolve();
  });
}

The example is using promises, but if your prefer you could use the next callback as well.

SetupRemoteHooks

Configures the defined remote hooks in the model.

Options

  • source (optional)
  • beforeRemote
  • afterRemote
  • afterRemoteError

Usage

The beforeRemote, afterRemote and afterRemoteError options should have the names of the remote methods you want to apply the hooks to.

Each remote method name is an object property that should contain a string or an array with the name(s) of the method(s) to be called.

If you define source, it will search the methods on that file, otherwise it will search the methods in the Model.

  "mixins": {
    "SetupRemoteHooks": {
      "source": "./common/models/employee-hooks.js",
      "beforeRemote": {
        "deleteById": ["checkSomething", "logSomething"],
      },
      "afterRemote": {
        "create": "doSomething"
      },
      "afterRemoteError": {
        "create": "doSomethingElse"
      }
    }
  }

The source file (employee-hooks.js in our example) would look like this:

module.exports = {
  doSomething,
  checkSomething,
  logSomething,
};

function doSomething(context, instance, next) {
  next();
}

function checkSomething(context, instance, next) {
  next();
}

function logSomething(context, instance, next) {
  next();
}

This example is not using promises, since it looks like they are not supported yet for remote hooks.

Credits

Created by c3s4r for Devsu.

Copyright Devsu LLC, 2016.

License: MIT