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-find-mixin

v0.0.5

Published

A mixin that assists with the _filter on related properties_ problem that is present when trying to filter using loopback. Unfortunately, this doesn't fully solve [issue 517](https://github.com/strongloop/loopback/issues/517) but mitigates it somewhat. Th

Downloads

2

Readme

Loopback Find Mixin

A mixin that assists with the filter on related properties problem that is present when trying to filter using loopback. Unfortunately, this doesn't fully solve issue 517 but mitigates it somewhat. This mixin implements this functionality on top of loopback, so that it should function with all existing datasource connectors.

Current problem

The filtering issue with the loopback ORM is that you cannot filter on related properties. For example, if you have a model set such as:

Customer belongsTo City belongsTo Country

You cannot easily find all customers which live in a country starting with A. Typically the way you'd get around this is either through:

  1. A custom SQL query, but you end up losing most of the filtering power of loopback as well as the property mappings
  2. Doing a query on countries which start with A then including the relations in the opposite direction, e.g. cities. Then finding people with cityIds in that set.

This mixin assists with option 2, which is going to be perfectly performant in some cases and not in others.

When to use this mixin

Any time that you would think it's fine to do multiple queries in the opposite direction anyway, then it would be reasonable to use.

Install

npm install --save loopback-find-mixin

Server Config

{
  "_meta": {
    "sources": [
      "loopback/common/models",
      "loopback/server/models",
      "../common/models",
      "./models"
    ],
    "mixins": [
      "loopback/common/mixins",
      "../node_modules/loopback-find-mixin",
      "../common/mixins"
    ]
  }
}

Model Config

  {
    "name": "Widget",
    "properties": {
      "name": {
        "type": "string",
      }
    },
    "mixins": {
      "Find" : {
        "remotes": ["find"]
      }
    }
  }

Options

remotes is an array of remote method names that this mixin will execute before.

Usage

In addition to the usual loopback filter parameters where, include, limit, fields and offset, this mixin exposes another parameter require. An example filter:

{
  "require": {
    "city.country": {
      "regexp": "^A"
    }
  }
}

This will give us the query referred to earlier (find all customers where the country starts with A). This filter is transformed into the following:

{
  "where": {
    "cityId": {
      "inq": [...]
    }
  }
}