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

graphql-extends-generator

v1.2.0

Published

A tiny module for creating extended graphQL enums, inputs and types

Downloads

4

Readme

GraphQL-extends-generator

A tiny module for creating extended graphQL enums, inputs and types. Just give it a path to source (or sources) and a path to extended (or two or ten or more). Start it and see extended by your extends source files.

Installation

Using npm:

$ npm i -S graphql-extends-generator

In Node.js:

const graphqlGenerateExtends = require('graphql-extends-generator');

graphqlGenerateExtends(
  [path.resolve('source.graphql'), path.resolve('generic.source.graphql')],
  [
    path.resolve('Cat/types.graphql'),
    path.resolve('Dog/types.graphql'),
    path.resolve('Student/types.graphql'),
    path.resolve('Teacher/types.graphql'),
  ],
  {
    forbiddenDirectives: ['default'],
    prefix: 'Prefix',
    postfix: 'Postfix',
  }
);
// details in example

In the same directories you will found extended graphQl types and etc. In this example they were call like typesGenerated. Give your params and change names.

Usage

When you generate extends data you can pass such params:

  • sourcePath: String / [String] - A path or an array of paths to the source files

  • extendsPath: String / [String] - A path or an array of paths to the extends files

  • options { prefix: String, postfix: String, forbiddenDirectives: [String] }

    • prefix - prefix of generated files (prefix='Extended', extends file name='Type.graphql', result=ExtendedType)
    • postfix - postfix of generated files (postfix='Extended', extends file name='Type.graphql', result=TypeExtended)
    • forbiddenDirectives - some directive names, that shouldn't get to the resulting file. For example, if you use Prisma DB and want to extend the datamodel file or source files is used by other services with their own directives.

Results

Person

You have this (source)

type Person {
  id:ID! @unique
  role: PersonRole @default(value: "MANAGER")
  name: String!
  phone: String!
}

input PersonCreateInput {
  role: PersonRole
  name: String!
  phone: String!
}

and this (extends)

type Student extends Person {
    group: String!,
    course: Int,
    marks: [Mark!]!
}

input StudentCreateInput extends PersonCreateInput {
    group: String!
    course: Int
}

forbiddenDirectives = ['default'] and result is

type Student {
  id: ID!  @unique
  role: PersonRole
  name: String!
  phone: String!
  group: String!
  course: Int
  marks: [Mark!]!
}

input StudentCreateInput {
  role: PersonRole
  name: String!
  phone: String!
  group: String!
  course: Int
}

Cat

You have this (source)

enum AnimalRole {
  PACK_LEADER
  ORDINARY
}

type Animal {
  id: ID!,
  name: String,
  role: AnimalRole @default(value: "ORDINARY")
}
// another source
type ListResponse<SomeType> {
  edges: [SomeType]
  count: Int
  page: Int
  justForourSmallParam: Boolean
}

and this (extends)

type Cat extends Animal {
  suit: String,
  avgClawsLength: Float,
  loves: [Cat]! @isSame
}

enum CatRole extends AnimalRole {
  HARMFUL_LONER
  HOME_PET
}

type CatsResponce extends ListResponse<Cat> {
  serverLoveCats: Boolean!
}

forbiddenDirectives = ['default'] and result is

type Cat {
  id: ID!
  name: String
  role: AnimalRole
  suit: String
  avgClawsLength: Float
  loves: [Cat]!  @isSame
}

type CatsResponce {
  edges: [Cat]
  count: Int
  page: Int
  justForourSmallParam: Boolean
  serverLoveCats: Boolean!
}

enum CatRole {
 PACK_LEADER
 ORDINARY
 HARMFUL_LONER
 HOME_PET
}```