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

sequelize-external-methods

v1.0.0

Published

Allows externally defined methods to be loaded onto a Sequelize Model

Downloads

5

Readme

sequelize-external-methods

  • Utilities for defining Model methods (proto, getter, setter, static) external to the Model definition file.
    • helps clean up the Model definition file
    • helps make testing easier as each method is independent of Sequelize / a Model so its dependency on them can be easily mocked

Usage

Cut to the chase and see a complete example usage in the example/ directory or follow the directions below:

  • Define your methods in an external directory
    • You can define these directory(ies) anywhere you'd like. But I recommend you use the pattern directory based Models to have Model directories with methods/ holding the methods for that model.
      • note: to use directory based Models requires a slightly modified models/index.js exporter file see here
    • You can name the method files anything you'd like
    • You can name the methods themselves anything you'd like
/models
  index.js <--- modified Sequelize Models exporter (above)
  user.js <--- standard Model def file
  payment/
    index.js <--- directory based Model def file
    methods/ <--- directory to compartmentalize methods from the Model def
      index.js <--- collects and exports Named Method Objects
      payment.statics.js
      payment.getters.js
      payment.setters.js
      payment.prototypes.js
      tests/ <--- testing dir
        payment.statics.test.js <--- corresponding method def testing files
        payment.getters.test.js
        payment.setters.test.js
        payment.prototypes.test.js
  • export the methods as Named Method Objects from models/index.js
    • they must be exported as Named Method Objects!

/methods/static-methods.js

// example of static methods
function doAStaticThing() {
  //
}

module.exports = {
  doAStaticThing,
};

/methods/index.js

const staticMethods = require('./static-methods');
// other Named Method Objects here

module.exports = {
  staticMethods,
  // export any other Named Method Objects
};
  • import the externally defined methods and the loadExternalMethods utility into your Model file
    • note call loadExternalMethods(Model, methods); at the end of the model file, just before the return Model;
      • this ensures that console.warn messages are emitted if any methods get overridden (in the case of mixing external and classic method definitions)
const methods = require('./methods'); // { staticMethods, prototypeMethods, ... }
const { loadExternalMethods } = require('sequelize-external-methods');

module.exports = (sequelize, DataTypes) => {
  const Model = sequelize.define(
    'Model',
    { ...attributes },
    { ...options },
  );

  // associations

  // other method definitions

  loadExternalMethods(Model, methods);
  // suppress warnings: loadExternalMethods(Model, methods, false);

  return Model;
}

Requirements

To use the loadExternalMethods utility from this package you must export the Named Method Objects from methods/index.js

  • the file name(s) and method names in their exported objects are arbitrary
  • all that is required is that each method file exports an object with method definitions inside of it

You can include / exclude any of the Named Method Objects. Whichever ones are exported from methods/index.js will be loaded onto the Model by loadExternalMethods.

models/modelName/methods/index.js

const staticMethods = require('');
const getterMethods = require('');
const setterMethods = require('');
const prototypeMethods = require('');

module.exports = {
  staticMethods,
  getterMethods,
  setterMethods,
  prototypeMethods,
};

Named Method Objects

  • staticMethods: loaded directly onto the Model def (static methods)
    • accessing the method: Model.staticMethodName
    • Sequelize equivalent: Model.staticMethodName = function() {...}
  • prototypeMethods: loaded into the Model.prototype (instance methods)
    • accessing the method: modelInstance.prototypeMethodName
    • Sequelize equivalent: Model.prototype.prototypeMethodName = function() {...}
  • getterMethods: loaded into the Model def getterMethods (instance methods)
    • these are standard property getters / virtual getters
    • note: these are accessed as properties on the instance
    • accessing the "method" (get property value): modelInstance.getterMethodName
  • setterMethods: loaded into the Model def setterMethods. (instance methods)
    • these are standard property seters / virtual setters
    • note: these are accessed as properties on the instance
    • accessing the "method" (set property value): modelInstance.setterMethodName = someNewValue

Sequelize equivalent for getter/setterMethods:

models/modelName/index.js

module.exports = (sequelize, DataTypes) => {
  const Model = sequelize.define(
    'Model',
    { ...attributes },
    {
      ...options,
      getterMethods: {
        getterMethodName: function() {...}
      },
      setterMethods: {
        setterMethodName: function() {...}
      }
    }
  );
}

Backwards compatibility

You can still define methods directly on the Model following standard Sequelize syntax (see equivalents above). Or you can mix and match external with standard definitions.

  • loadExternalMethods will merge with whatever methods exist on the Model at the time of calling
  • if there is a naming conflict between a pre-defined method and an externally-loaded method a console.warn message will be emitted
    • warning shape: Existing [<location>] method [<method name>] overridden by loadExternalMethods
    • possible location values: getterMethods, setterMethods, prototype, static
  • recommended: call loadExternalMethods at the end of the Model def file to ensure warnings are provided for naming conflicts

models/modelName/index.js

const methods = require('./methods'); // { staticMethods, prototypeMethods, ... }
const { loadExternalMethods } = require('sequelize-external-methods');

module.exports = (sequelize, DataTypes) => {
  const Model = sequelize.define(
    'Model',
    { ...attributes },
    {
      ...options,
      getterMethods: { // optionally define using standard Sequelize syntax
        getterMethodName: function() {...}
      },
      setterMethods: { // optionally define using standard Sequelize syntax
        setterMethodName: function() {...}
      }
    }
  );

  // optionally define other method definitions / associations up here

  // last call before returning the Model def to ensure warnings are emitted for naming conflicts
  loadExternalMethods(Model, methods);

  // or to suppress override warnings (for whatever insane reason you have)
  loadExternalMethods(Model, methods, false);
  return Model;
}

How to define Sequelize models as directories instead of files

  • A predicate to defining external methods (while keeping the code organized) is to keep Model and method definitions in a directory rather than a single file
  • To do this requires a slight modification to the default (sequelize init) models/index.js file
  • This modification is backwards compatible and supports both Model files and directories
    • A model directory should have its name as the Model and its Model definition exported in its index.js file

models/index.js

'use strict';

var fs        = require('fs');
var path      = require('path');
var Sequelize = require('sequelize');
var basename  = path.basename(__filename);
var env       = process.env.NODE_ENV || 'development';
var config     = require(__dirname + '/../config/config.js')[env];
var db        = {};

var sequelize = new Sequelize(config.database, config.username, config.password, config);

fs
  .readdirSync(__dirname)
  .filter(file => file !== basename)
  .forEach(file => {
    const isDirectory = file.slice(-3) !== '.js';
    const importPath = isDirectory ? [__dirname, file, 'index.js'] : [__dirname, file];
    
    var model = sequelize['import'](path.join(...importPath));
    db[model.name] = model;
  });

Object.keys(db).forEach(modelName => {
  if (db[modelName].associate) {
    db[modelName].associate(db);
  }
});

db.sequelize = sequelize;
db.Sequelize = Sequelize;

module.exports = db;

Here is the modified portion if you want to add it to a models/index.js exporter that you have already customized by other means:

fs
  .readdirSync(__dirname)
  .filter(file => file !== basename)
  .forEach(file => {
    const isDirectory = file.slice(-3) !== '.js';
    const importPath = isDirectory ? [__dirname, file, 'index.js'] : [__dirname, file];
    
    var model = sequelize['import'](path.join(...importPath));
    db[model.name] = model;
  });

Example

Say we have the follow structure to our models/ dir:

  • our user.js file holds the User Model definition (standard practice)
  • our payment/ dir holds its Payment Model definition in its underlying payment/index.js file
  • using the modified models/index.js file above - both model definitions are correctly loaded
/models
  index.js <--- modified Sequelize Models exporter (above)
  user.js <--- standard Model def file
  payment/
    index.js <--- directory based Model def file
    methods/ <--- directory to compartmentalize methods from the Model def
      index.js

loadExternalMethods and utilities

You can use them individually but the recommended usage is with loadExternalMethods itself since you can load as many or as few external methods as you'd like with it. Whatever Named Method Objects it receives will be loaded onto the target Model. If you choose to only load a specific set you can use the following utilities.

Utilities

loadGetters: only loads (instance) getterMethods

/**
 * Loads virtual getter methods onto the Model
 * - same as setting in model options.getterMethods of sequelize.define()
 *  - merges with any methods defined in options.getterMethods
 * - emits console.warn if a getter method is overridden during merging
 *  - disable with warn false (default - true)
 * - mutates:
 *  - Model.prototype._customGetters (merges with each method from getterMethods arg)
 *  - Model.prototype._hasCustomGetters (increments for each non-override method added)
 * @param {object} Model Model to add prototype getter methods
 * @param {object} getterMethods { methodName: function() { ... }, ... }
 * @param {boolean} warn [true] set false to suppress merge override warning
 */
const loadGetters = (Model, getterMethods, warn = true) => {
  for (const getterName of Object.keys(getterMethods)) {
    const methodWillOverride = getterName in Model.prototype._customGetters;
    if (methodWillOverride) {
      warn && console.warn(overrideWarning('getterMethods', getterName));
    }
  }
  Model.options.getterMethods = { ...Model.options.getterMethods, ...getterMethods };
  Model.refreshAttributes();
};

loadSetters: only loads (instance) setterMethods

/**
 * Loads virtual setter methods onto the Model
 * - same as setting in options.setterMethods of sequelize.define()
 *  - merges with any methods defined in options.setterMethods
 * - emits console.warn if a setter method is overridden during merging
 *  - disable with warn false (default - true)
 * - mutates:
 *  - Model.prototype._customSetters (merges with each method from setterMethods arg)
 *  - Model.prototype._hasCustomSetters (increments for each non-override method added)
 * @param {object} Model Model to add prototype setter methods
 * @param {object} setterMethods { methodName: function() { ... }, ... }
 * @param {boolean} warn [true] set false to suppress merge override warning
 */
const loadSetters = (Model, setterMethods, warn = true) => {
  for (const setterName of Object.keys(setterMethods)) {
    const methodWillOverride = setterName in Model.prototype._customSetters;
    if (methodWillOverride) {
      warn && console.warn(overrideWarning('setterMethods', setterName));
    }
  }
  Model.options.setterMethods = { ...Model.options.setterMethods, ...setterMethods };
  Model.refreshAttributes();
};

loadStatics: only loads static (Model) methods

/**
 * Loads static methods onto the Model
 * - merges with any methods defined directly on Model
 * - emits console.warn if a static method is overridden during merging
 *  - disable with warn false (default - true)
 * - mutates:
 *  - Model (merges)
 * @param {object} Model Model to add static methods
 * @param {object} staticMethods { methodName: function() { ... }, ... }
 * @param {boolean} warn [true] set false to suppress merge override warning
 */
const loadStatics = (Model, staticMethods, warn = true) => {
  for (const [staticName, method] of Object.entries(staticMethods)) {
    if (staticName in Model) {
      warn && console.warn(overrideWarning('static', staticName));
    }
    Model[staticName] = method;
  }
}

loadPrototypes: only loads prototype (instance) methods

/**
 * Loads prototype (instance) methods onto the Model
 * - merges with any methods defined in Model.prototype
 * - emits console.warn if a prototype method is overridden during merging
 *  - disable with warn false (default - true)
 * - mutates:
 *  - Model.prototype (merges with each method from prototypeMethods arg)
 * @param {object} Model Model to add prototype methods
 * @param {object} prototypeMethods { methodName: function() { ... }, ... }
 * @param {boolean} warn [true] set false to suppress merge override warning
 */
const loadPrototypes = (Model, prototypeMethods, warn = true) => {
  for (const [prototypeName, method] of Object.entries(prototypeMethods)) {
    if (prototypeName in Model.prototype) {
      warn && console.warn(overrideWarning('prototype', prototypeName));
    }
    Object.defineProperty(Model.prototype, prototypeName, {
      value: method,
      enumerable: true,
    });
  }
}