ksaldana1

ts.forEachChild(source, node => {
  if (ts.isTypeAliasDeclaration(node)) {
    console.log(node.kind);
  }
})
// prints TypeAliasDeclaration

ksaldana1

import { protos } from 'my_company_protos'

export type User = protos.user.User;

ksaldana1

import { EventObject } from 'xstate';

interface StateSchema<TEvents extends EventObject, TAllStates extends string> {
  states?: { [K in TAllStates]: StateNode<TEvents, TAllStates> };
}
interface StateNode<
  TEvents extends EventObject,
  TAllStates extends string,
  TContext = any
> extends StateSchema<TEvents, TAllStates> {

ksaldana1

{
  "vim.easymotion": true,
  "vim.easymotionMarkerHeight": 20,
  "vim.easymotionMarkerWidthPerChar": 12,
  "vim.easymotionMarkerFontSize": "16",
  "vim.easymotionMarkerBackgroundColor": "#428aff",
  "vim.easymotionMarkerForegroundColorOneChar": "#fffcfc",
  "vim.easymotionMarkerForegroundColorTwoChar": "#fffcfc",
  "vim.easymotionMarkerFontFamily": "Arial", 
  "vim.normalModeKeyBindingsNonRecursive": [

ksaldana1

// 1) Types that have a common, singleton type property — the discriminant.
// In this example the "kind" property is the discriminant.
interface Square {
    kind: "square";
    size: number;
}

interface Rectangle {
    kind: "rectangle";
    width: number;

ksaldana1

Domain Modeling with Tagged Unions in GraphQL, ReasonML, and TypeScript

GraphQL has exploded in popularity since its open-source announcement in 2015. For developers who had spent a lot of time managing data transformations from their back-end infrastructure to match front-end product needs, GraphQL felt like a tremendous step forwards. Gone were the days of hand-writing BFFs to manage problems of over-fetching.

A lot of value proposition arguments around GraphQL have been about over/under fetching, getting the data shape you ask for, etc. But I think GraphQL provides us more than that—it gives us an opportunity to raise the level of abstraction of our domain, and by doing so allow us to write more robust applications that accurately model the problems we face in the real world (changing requirements, one-off issues).

An underappreciated feature of GraphQL is its type system, and in particular features like [union types](https:

ksaldana1

// 1) Types that have a common, singleton type property — the discriminant.
// In this example the "kind" property is the discriminant.
interface Square {
    kind: "square";
    size: number;
}

interface Rectangle {
    kind: "rectangle";
    width: number;

ksaldana1

interface Square {
    kind: "square";
    size: number;
}

interface Rectangle {
    kind: "rectangle";
    width: number;
    height: number;
}

ksaldana1

function assertNever(x: never): never {
    throw new Error("Unexpected object: " + x);
}
function area(s: Shape) {
    switch (s.kind) {
        case "square": return s.size * s.size;
        case "rectangle": return s.height * s.width;
        case "circle": return Math.PI * s.radius ** 2;
        default: return assertNever(s); // error here if there are missing cases
    }

ksaldana1

type Query {
  messages: [Message!]!
}

type Message {
  id: ID!
  text: String!
  author: MessageAuthor!
}