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-nested-filter-mixin

v0.1.3

Published

A workaround mixin to enable a behavior similar to a nested query filter

Downloads

91

Readme

loopback-nested-filter-mixin

Features

  • workaround to provide a functionality equivalent to nested queries
  • remove all or only some of the entries that do not respect the criteria

Description

This mixin is a workaround to an issue with loopback that does not allow to queries to filter based on nested properties. This is not a patch the connectors.

Installation

npm install loopback-nested-filter-mixin --save

How to use

Add the mixin property to your server/model-config.json like the following:

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

Add the mixin attribute to the definition of all Models you want to use it with.

{
  "name": "app",
  "properties": {
    "name": {
      "type": "string",
    }
  },
  "relations": {
    "users": {
      "type": "hasMany",
      "model": "user",
      "foreignKey": "appId",
      "through": "userRole"
    }
  },
  "mixins": {
    "NestedFilter": null
  }
}

Usage

When filtering on nested objects, the user should specify his conditions in the include filter, according to the following example (using the Appointment example from docs). In this case, we want to get the information of any patient that has an appointment with any Doctor named Strange.

GET /patients?filter={"include":[{
  "relation": "appointment",
  "scope": {
    "include": [{
      "relation": "physician",
      "scope": {
        "where": {"name": "Strange"}
      }
    }]
  }
  }],
  "excludeIfEmpty": true  
}

The mixin is configured to support two different filtering behaviours:

  1. Remove any entry it finds where the includes generated an empty list.

(Loopback's default behaviour would be to return every patient.appointment either with Strange's info or an empty list)

{
  "where": "...",
  "include": "...",
  "excludeIfEmpty": true
}
  1. Remove any entry it finds where the includes generated an empty list and the user set it as an exclusion criteria.
{
  "where": "...",
  "include": [{
    "relation": "appointment",
    "scope": {
      "include": [{
        "relation": "physician",
        "scope": {
          "where": {"name": "Strange"},
          "include": [{
            "relation": "university",
            "scope": {
              "where": {"name": "Harvard"}
            }
          }]
        }
      }]
    }
    }],
  },
  "excludeIfEmpty": ["appointment.physician"]
}

In this case, we want to get the info of every Patient that has an Appointment with a Doctor named Strange and, in case he went to Harvard, we want to retrieve that information. But we don't want it to be an exclusion criteria.

License

MIT