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

dataql

v1.0.9

Published

Fetching data by query from js object

Downloads

27

Readme

DataQl

Fetching data by query from js object

dataql

How to install?

npm i dataql

How it works:

So you have some object with functions which return some data

  const resolvers = {
    post() {
      return {
        post: {
          _id: 1,
          name: 'Igor',
          hello: 'world',
        },
      }
    }

    postComments(post) {
      const comments = [
        {
          _id: 1,
          description: 'Hello world!',
          postId: 1,
        },
        {
          _id: 2,
          description: 'Hello universe!',
          postId: 1,
        },
        {
          _id: 3,
          description: 'Hello universe!',
          postId: 2,
        },
      ]

      return comments.filter(comment => comment.postId == post.id)
    }
  }

also you have a query

  const query = {
    post: {
      _id: null,
      name: null,
      comments: [
        _id: null,
        description: null,
      ],      
    }
  }

just fetch data by query from resolvers

const dataql = require('dataql')

dataql({ query, resolvers }).then((data) => {
  /*
    console.log(data) =>
    {
      post: {
        _id: 1,
        name: 'Igor',
        comments: [
          {
            _id: 1,
            description: 'Hello world!',
          },
          {
            _id: 2,
            description: 'Hello universe!',
          },        
        ]
      },
    }
  */
})

Typization

If you query object or array, your resolvers should return same type. In another case it will trigger error. For null query you can return anything.

API

dataql(args)

return: Promise

args Object | {}

args.query Object | null

query object where null is any possible value which return resolver.

if your resolver contain an array you should define this in query like this example above

args.entities Object | null

object which contains data, first it search data in here if he doesnt found he find in resolver

args.resolvers Object | null

object which contains functions called resolvers. resolvers should return a data

resolver can be a sync function or

args.root Object | null

data object passed to first level resolvers

args.params Object | null

query params which passed to every resolver

args.context Object | null

context object which passed to every resolver

args.info Object | { query: {} }

args.info.query Object | null

query object for resolver

resolver(root, params, context, query)

root Object | null

object from parent resolver

params Object | null

query params

context Object | null

context payload

query Object | { query: {} }

query for current resolver