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

relay-transform-scalar

v3.0.0

Published

Parse and serialize scalars into complex objects (e.g. dates) with relay

Downloads

4

Readme

Relay Parse Scalar

Parse scalars into complex objects (e.g. dates) and serialize them before executing a GraphQL network function.

Usage

Note: This README uses ISO8601DateTime as an example.

relay.config.json

{
  // ...
  "customScalarTypes": {
    "ISO8601DateTime": "Date"
  }
}

Relay setup

// ...
import RelayDefaultHandlerProvider from "relay-runtime/lib/handlers/RelayDefaultHandlerProvider";

import {
  configOption,
  isParseScalarHandle,
  parseScalarHandle,
  serializeVariables
} from "relay-transform-scalar"

const config = [
  configOption({
    parse: (dateString) => typeof dateString === "string" ? parse(dateString) : null, // your parse logic here
    parseType: "ISO8601DateTime",
    serialize: (date) => date ? format(date) : null, // your serialization logic here
    serializeTest: (value) => value instanceof Date // test if this config option should be used for serialization
  })
]

function handlerProvider(handle: string) {
    if (isParseScalarHandle(handle)) return parseScalarHandle(config)
    // ...
    return RelayDefaultHandlerProvider(handle);
}

export const fetchFn = async (request: RequestParameters, variables: Variables) => {
    const body = {
       // ...
       variables: serializeVariables(variables, config)
    }

    // ...

    return resp.json()
}

const createNetwork = () =>  {
  const fetchResponse = async(/* ... */) => {

    // ...

    return fetchFn(params, variables)
  }

  return Network.create(fetchResponse, subscriptionHandler)
}

Marking fields for parsing

Right now you have to insert this GraphQL directive for every field of type ISO8601DateTime otherwise your typescript types will be wrong (the field would be of type Date but at runtime it really is a string because no transformation happened).

// ...

graphql\`
  fragment Something on SomeType {
    someField @__clientField(handle: "parseScalar(ISO8601DateTime)")
  }
\`

How it works

  1. Using the above relay config the compiler inserts types for fields which are of the ISO8601DateTime type. Any time a variable or field has the ISO8601DateTime GraphQL type the generated type will be Date.

  2. The relay environment is configured to do two things:

  • Whenever a field with the parse directive is encountered, it receives a handler for that field which parses the field according to your config and sets it on the record (in a hack-ish way though).

  • Whenever a GraphQL network function is called (in the example from above via fetch) the variables are serialized.