Maybe using a meta param?

Instead of interface FooInterface {}, it would be interface FooShape {}, so that any prop types would automatically be typed!

The provided types are currently not exported.

TypeScript + PropTypes = win.

The generated shapeshifter file (usually an index.js file) encounters a ton of churn any time a schema changes. This can cause merge conflicts when 2 separate branches generate a new output file.

Perhaps support a magic import path, like import { SomeShape } from 'shapeshifter/schemas';, which will automatically generate the shapeshifter file during a build process (webpack), instead of including the generated file in the source code.

Pros:

• No build command needs to be run
• No file committed to source
• No possibility of conflicts

Cons:

• Breaks IDE/editor import lookups and references
• Not apparent whether a schema/type/constant is supported (unless looking for the JSON files)

I am using a custom directive, that looks like this:

enum AuthRole {
  VERIFIED
  PAID
  ADMIN
  DEV
}
directive @auth(role: AuthRole, roles: [AuthRole]) on FIELD | FIELD_DEFINITION

I have this defined in my graphql file.

When I run shapeshifter with shapeshifter-parser-graphql, I get this error:

shapeshifter --prop-types src/generated/data-server.graphql > src/generated/data-server.props.js

Unsupported GraphQL definition "auth".

Is there a way to ignore directives?

New methods:

• morphTo
• morphMany

And for define:

schema.define({
  morphTo: [a, b, c],
  morphMany: [[a, b, c]],
});

Any way to support it? Also, any chance to support migrations or depreciations since types change over time?

When transpiling files on the command line.

To the top of the built file, so everyone knows it's generated.

Should be renamed to burnside.

Otherwise TS errors with:

src/schemas/lantern.ts:110:34 - error TS2345: Argument of type 'Requireable<any> | (() => void)' is not assignable to parameter of type 'Validator<any>'.
  Type '() => void' is not assignable to type 'Validator<any>'.
    Type 'void' is not assignable to type 'Error | null'.

110   attachments: PropTypes.arrayOf(TicketAttachmentShape),

Which causes builds to fail.

Add a basic define method to map relations using GQL syntax.

schema.define({
  user: UserSchema,
  posts: [PostSchema],
});

As the title states. This allows prop types to be generated while schemas can be optional.

Since nullable and optional are really not the same thing.

Supports: has one, has many, belongs to, belongs to many

It is currently not built and included when published.

Allow shapes to be defined as references within the JSON file, so that they can be reused without having to declare external JSON files.

{
  "name": "string",
  "references": {
    "Foo": {
      "a": "string",
      "b": "bool",
      "c": "number",
    }
  },
  "attributes": {
    "bar": {
      "type": "reference",
      "reference": "Foo"
    }
  }
}

It fails on this line:

references[definition.valueType.config.reference].name

Can be changed to something like:

const name = definition.valueType.config.self
  ? this.reader.name
  : references[definition.valueType.config.reference].name;

We also need to change the output from this:

export const PaymentSchema = new Schema('payments')
  .hasMany({
    refunds: PaymentSchema,
  });

To something like this:

export const PaymentSchema = new Schema('payments');

PaymentSchema.hasMany({
  refunds: PaymentSchema,
});

As the title states.

Enum gets annoying with TS.