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-save-relation-mixin

v1.1.2

Published

A mixin to automatically save related Models

Downloads

24

Readme

Loopback save relation mixin

What does this do?

It provides a way to save related models when creating records.

For example if the model ApplicationUser hasOne Profile you will be able to send:

PATCH /api/ApplicationUsers

{ 
  "email": "[email protected]",
  "password": "123456",
  "profile": {
    "name": "user 1"
  } 
}

How does this work?

First you must install this package through npm

$ npm install loopback-save-relation-mixin --save

Then you have to configure the file model-config.json to load the mixin.

"mixins": [
  ...
  "../node_modules/loopback-save-relation-mixin",
  ...]

And finally you can configure your model so it enables saving a related model.

{
  "name": "ApplicationUser",
  "base": "User",
  "idInjection": true,
  "options": {
    "validateUpsert": false
  },
  "mixins": {
    "SaveRelation": {
      "relations": ["profile", "orders", "projects", "tickets"]
    }
  },
  "relations": {
    "profile": {
      "type": "hasOne",
      "model": "Profile",
      "foreignKey": "userId"
    },
    "orders": {
      "type": "hasMany",
      "model": "Order",
      "foreignKey": "userId"
    },
    "projects": {
      "type": "hasMany",
      "model": "Project",
      "foreignKey": "userId",
      "through": "UserProject"
    },
    "tickets": {
      "type": "hasAndBelongsToMany",
      "model": "Ticket"
    }
  }
}

It works for:

  the loopback saveRelation mixin
    given a hasOne relation type
      ✓ should be saved
      ✓ should be updated
      ✓ should be deletable by sending an empty object
      ✓ should be deletable by sending null
    given a hasMany relation type
      ✓ should be saved
      ✓ should be updated
      ✓ should able to remove one relatedObject
      ✓ should able to remove all the relatedObjects by sending null
      ✓ should able to remove all the relatedObjects by sending an empty array
      ✓ should be updatable and deletable in the same operation
    given a hasManyThrough relation type
      ✓ should create the relatedObjects if they do not exist in the database and save the relations
      ✓ should be saved if the related objects do exist in the database
      ✓ should be deletable
    given a hasAndBelongsToMany relation type
      ✓ should create the relatedObjects if they do not exist in the database and save the relations
      ✓ should be saved if the related objects do exist in the database
      ✓ should be deletable