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

@moilandtoil/sealab-type

v0.0.5

Published

GraphQL type object with sealab-application dependency injection

Downloads

3

Readme

Overview

Sealab-type allows for the creation of extendable GraphQL types with dependency injection. Also includes a type manager for registering the types with a sealab-schema-builder instance.

Usage

Create type objects by extending the BaseType class. Configure the type name and definition in the constructor and define a resolver function. The helper methods service, logger, debug, info, and error will then be available to the resolver.

BaseType

The base type is an extendable class, which should implement a constructor and resolver method. The constructor should accept the parameter of application, and call the parent constructor, passing it. The constructor should define the properties typeName and typeDef. The resolver should return an object that will resolve the typeDef.

TypeManager

The type manager should be instantiated with a SchemaBuilder object from the sealab-schema-builder repo. It has two methods, registerType and registerTypes. The first parameter for these methods should be a single class definition or array of class definitions respectively. The second parameter should be the application container.

Example

class CoolType extends BaseType {
  constructor(application) {
    super(application);
    this.typeName = "CoolType";
    this.typeDef = `
      type ValidType {
        id: String
        name: String,
        related_resource: [WhateverResource]
      }
    `
  }

  resolver() {
    return {
      id: (value) => {
        return value.id;
      },
      name: (value) => {
        return value.name;
      },
      related_resource: async (value) => {
        this.debug("Fetching related resources by the parent id");
        return await this.service("whatever_resource").getResourcesByRelatedId(value.id);
      }
    }
  }
}

Notes:

Pay attention to the scope of this. The resolver is called by an execute function which returns the object of functions. This is passed to the SchemaBuilder, which registers it with GraphQL.

The point being, assume you have no idea what calls it. So you need to ensure the scope of this is the class that extends the BaseType class. Either use the arrow operator when defining the resolver, assign this to a variable outside the object definition, ie.

resolver(root, args, context) {
  const type = this;
  return {
    foo: function(value) => {
      type.debug("Calling object `this` through variable assigned in outer scope");
    }
  }
}