Sequelize Paper Trail

Track changes to your models, for auditing or versioning. See how a model looked at any stage in its lifecycle, revert it to any version, or restore it after it has been destroyed. Record the user who created the version.

Table of Contents

• Sequelize Paper Trail
  • Table of Contents
  • Installation
  • Usage
    • Example
  • User Tracking
  • Disable logging for a single call
  • Options
    • Default options
    • Options documentation
  • Limitations
  • Testing
  • Support
  • Contributing
  • Author
  • Thanks
  • Links

Installation

npm install --save sequelize_paper_trail

Note: the current test suite is very limited in coverage.

Usage

Sequelize Paper Trail assumes that you already set up your Sequelize connection, for example, like this:

const Sequelize = require('sequelize');
const sequelize = new Sequelize('database', 'username', 'password');

then adding Sequelize Paper Trail is as easy as:

const PaperTrail = require('sequelize_paper_trail').init(sequelize, Sequelize, options);
PaperTrail.defineModels();

which loads the Paper Trail library, and the defineModels() method sets up a versions table.

Note: If you pass userModel option to init in order to enable user tracking, userModel should be setup before defineModels() is called.

Then for each model that you want to keep a paper trail you simply add:

Model.hasPaperTrail();

hasPaperTrail returns the hasMany association to the versionModel so you can keep track of the association for reference later.

Example

const Sequelize = require('sequelize');
const sequelize = new Sequelize('database', 'username', 'password');

const PaperTrail = require('sequelize_paper_trail').init(sequelize, Sequelize, options || {});
PaperTrail.defineModels();

const User = sequelize.define('User', {
  username: Sequelize.STRING,
  birthday: Sequelize.DATE
});

User.Versions = User.hasPaperTrail();

User Tracking

There are 2 steps to enable user tracking, ie, recording the user who created a particular revision.

1. Enable user tracking by passing userModel option to init, with the name of the model which stores users in your application as the value.

const options = {
  /* ... */
  userModel: 'user',
};

2. Pass the id of the user who is responsible for the database operation to sequelize_paper_trail either by sequelize options or by using continuation-local-storage.

Model.update({
  /* ... */
}, {
  userId: user.id
}).then(() {
  /* ... */
});

OR

const createNamespace = require('continuation-local-storage').createNamespace;
const session = createNamespace('my session');

session.set('userId', user.id);

Model.update({
  /* ... */
}).then(() {
  /* ... */
});

To enable continuation-local-storage set continuationNamespace in initialization options. Additionally, you may also have to call .run() or .bind() on your cls namespace, as described in the docs.

Disable logging for a single call

To not log a specific change to a versioned object, just pass a noPaperTrail with a truthy (true, 1, ' ') value.

const instance = await Model.findOne();
instance.update({ noPaperTrail: true }).then(() {
  /* ... */
});

Options

Paper Trail supports various options that can be passed into the initialization. The following are the default options:

Default options

// Default options
const options = {
  debug: false,
  log: null,
  exclude: [
    'id',
    'createdAt',
    'updatedAt',
    'deletedAt',
    'created_at',
    'updated_at',
    'deleted_at',
  ],
  versionModel: 'Version',
  tableName: 'versions',
  underscored: false,
  underscoredAttributes: false,
  versionAttributes: {
    itemId: 'itemId',
    itemType: 'itemType',
    object: 'object',
    objectChanges: 'objectChanges',
    userModelAttribute: 'whodunnit',
  },
  userModel: false,
  continuationNamespace: null,
  continuationKey: 'userId',
  mysql: false,
};

Options documentation

Limitations

• This project does not support models with composite primary keys. You can work around using a unique index with multiple fields.

Testing

The tests are designed to run on SQLite3 in-memory tables, built from Sequelize migration files. If you want to actually generate a database file, change the storage option to a filename and run the tests.

npm test
# or with yarn:
# yarn test

Support

Please use:

• GitHub's issue tracker

Contributing

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Added some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

Author

© OlympusOne – @olympusone – support@olympusone.com Distributed under the MIT license. See LICENSE for more information. https://github.com/olympusone/sequelize_paper_trail

Thanks

This project was inspired by:

• Sequelize Paper Trail
• Sequelize-Revisions
• Paper Trail

Contributors: https://github.com/olympusone/sequelize_paper_trail/graphs/contributors

Links

• Example application