jcmais/nexus-plugins

A collection of plugins for nexus https://github.com/graphql-nexus/schema

🗨 My name is Jonathan Cardoso, I'm a Full-Stack Developer since 2011, currently living in Curitiba, PR - Brazil and working remotely at Teamflow, helping shape the future of remote work.

👨‍💻 My favorites languages, tech and libraries are: TypeScript, Node.js, GraphQL, TypeScript, React and did I say that I love TypeScript?

⚙ If given the opportunity, I seek to be [one of] the DevOps person - I have experience with most CI platforms, deployments tools, and cloud providers - Currently using Terraform and Kubernetes on GCP.

📚 Learning Elixir and game development using the Unity Editor - Loving both ❤ - Planning to learn Rust at some point in 2021

🕹 Playing video games since I was kid, favorites genres are: (J)RPGs, Turn-Based, Survival, Sci-fi and Roguelike

✍ Blog

🤩 Perfect job would be 60% Backend, 25% DevOps, and 15% Frontend

🌐 You can also find me on:

• twitter
• linkedin

🙋‍♂️ Pronouns: He/Him

⚡ Fun Fact: I've a Bachelor's Degree in Accounting, but I never worked as an Accountant.

🎶 🎶 🎶

Contributions on GitLab in the last year

nexus-plugins's Issues

0.2.0 does not contain optional config field in relay global id plugin

Hi there,

I might be wrong, but I now replace my custom published package with 0.2.0 because I assumed the optional config param was resolved with that version. It should contain the fix merged with #4 . But it doesn't.

Did something go wrong when you published the package?

Generated type mismatch

Since updating to @jcm/nexus-plugin-relay-mutation 0.1.2, TypeScript types generated by Nexus do not align with the actual input argument passed to mutateAndGetPayload.

For example, if I created a Relay mutation as follows

  t.relayMutation('foo', {
    inputFields(it) {
      it.nonNull.string('bar');
    },
    outputFields(ot) {
      ot.nonNull.string('baz');
    },
    mutateAndGetPayload(_root, inputFields) {
      return {baz: inputFields.bar};
    },
  });

TypeScript will expect the type of inputFields to be

inputFields: {
  input: {
    baz: string;
    clientMutationId?: string | null | undefined;
  };
}

meanwhile the actual type is

inputFields: {
  baz: string;
  clientMutationId?: string | null | undefined;
}

Field "id" missing in typescript definition when using plugin

When I use the plugin and define id as a relayGlobalId field, it results in a type error stating that "id" is not found on the object. If I use the model ID instead of relay (uncomment line below), there is no type error, but the id is obviously not relay-compliant. I'm not sure if this is related to graphql-nexus/nexus#36 (see comment), but is there any way to get nexus to realize the id does exist on the root type?

const Task = objectType({
  name: TaskModel.$name,
  definition: (t) => {
    t.implements('Node')
    t.relayGlobalId('id', {})
    // t.field(TaskModel.id.name, TaskModel.id)
    t.connectionField('comments', {
      type: 'Comment',
      resolve: async (src, args, ctx, info) => {
        const comments = db.comment.find({
          where: {
            taskId: src.id, // <==== TypeError Here
          },
        })
      },
    })
  },
})