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

gql-cf

v0.0.2

Published

A GraphQL Conditional Fields utility using template literals

Downloads

3

Readme

GraphQL Conditional Fields

If you've stumbled upon this randomly... well you're probably in the wrong neighborhood, to be honest.

In attempting to consolidate queries shared between 6 different repositories, but with very slight variations on the queries themselves (added or missing fields, etc), I came upon the idea of making these things conditional.

Now, if you're a fervent user of GraphQL you might recoil in horror at the thought of conditional queries, since the entire point of GraphQL is for queries to be individual, but, for our purposes, it works fine.

Currently not really useable

I mean, honestly, this is harcoded with a Typescript definition for the data we're sending to it, which means, you probably can't use it as-is. But... well, stay tuned for a more generic version sooner or later (probably later, lots to do lots to do!)

Usage

Start by installing this thing:

npm i gql-cf
or
yarn add gql-cf

Then, initialize it with the required values. This should be done in your index.js or app.js, as close to the top as possible, before any components using it load up.

import { ConditionalField } from 'gql-cf'

ConditionalField.init({
  web: true,
  resident: true
})

With that being done, you can now call queries in a dynamic fashion. This is done by using the cf template literal tag, and inserting functions within the template literal to conditionally add fields. I'm not sure how to actually describe this in technical terms, my brain is mush right now, but here's an example of what I mean:

import { gql } from '@apollo/client'
import { ConditionalField } from 'gql-cf'
const { cf } = ConditionalField

export const USER_FIELDS = cf`
  id
  username
  firstName
  lastName
  ${t => t.web && `
  lastLogin
  avatar
  `}
  ${t => t.mobile && `
  tinyAvatar
  lastMobileLogin
  `}
  ${t => t.manager && `
  passwordStrength
  email
  signupDate
  payment {
    method
    price
    lastPayment
  }
  `}
`

How's this useful? Well, for each of our project we just define the context, then use this context to filter out the fields we need.

Marvelous. And, again, I cannot stress this enough: probably useless to you right now and maybe ever. So... uhm... don't... use it? I guess?