This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency eslint-plugin-jest to v27
• chore(deps): update dependency eslint-plugin-prettier to v5
• chore(deps): update dependency fs-extra to v11
• chore(deps): update dependency husky to v8
• chore(deps): update dependency lint-staged to v14
• chore(deps): update dependency prettier to v3
• chore(deps): update dependency rimraf to v5
• chore(deps): update dependency rollup to v3
• chore(deps): update dependency semantic-release to v22
• chore(deps): update node.js to v17
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• chore(deps): update dependency graphql-tag to v2.12.6
• chore(deps): update dependency cross-env to v7
• chore(deps): update dependency cz-conventional-changelog to v3

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): replace dependency babel-eslint with @babel/eslint-parser
• chore(deps): update node.js to 44c6136
• chore(deps): update dependency babel-eslint to v10
• chore(deps): update dependency eslint to v8
• chore(deps): update dependency fetch-mock to v9
• chore(deps): update dependency graphql to v16
• chore(deps): update jest monorepo to v29 (major) (babel-jest, jest)
• fix(deps): update dependency graphql-tools to v9
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

This is so amazing!!! Any interest in us moving it to the apollographql org and having the apollo team help out in this?

Also I just want to say how incredibly thankful I am for people like you in the community to push the boundaries of GraphQL with such enthusiasm and vigor! People like you make our jobs so much more enjoyable and fun!

So thanks! 🤗

I've realized I have no way to resolve error of server response, looks like this line ignored server error and did nothing. I expected that can be resolved to errors of GraphQL response, is this lib have any plans to support or PR welcome? 😃

Hi,

This query:

{
  input: {
    name: 'yellow'
  }
}

As far as I know, we can’t get the following request body by editing the body directive parameter:

{
  name: 'yellow'
}

As discussed in #12, it would be great to support mapper functions for the body, query and provides directive parameters (in the spirit of mapper). Mapper functions would allow to map to anything, including the example above.

Hi,

Here is a new test that currently fails:

diff --git a/src/__tests__/schema-generator.test.js b/src/__tests__/schema-generator.test.js
index 1f77b11..5d2ea0c 100644
--- a/src/__tests__/schema-generator.test.js
+++ b/src/__tests__/schema-generator.test.js
@@ -25,2 +25,6 @@ const typeDefs = gql`
 
+  input ColorInput {
+    name: String!
+  }
+
   type Mutation {
@@ -33,2 +37,7 @@ const typeDefs = gql`
       )
+    createColor(input: ColorInput!): Color
+      @rest(
+        route: "/colors"
+        method: "POST"
+      )
   }
@@ -201,2 +210,45 @@ describe(`General`, () => {
 
+  it(`supports a mutation with an input type`, async () => {
+    expect.assertions(2)
+
+    const fetcher = fetchMock
+      .sandbox()
+      .post('/colors', (url, opts) => {
+        const data = opts.body && JSON.parse(opts.body)
+        expect(data).toEqual({
+          name: 'yellow',
+        })
+
+        return JSON.stringify({
+          id: 'yellow',
+          name: 'yellow',
+        })
+      })
+
+    const schema = createRestSchema({ fetcher })
+    const mutation = `
+      mutation CreateColor($input: ColorInput!) {
+        createColor(input: $input) {
+          id
+          name
+        }
+      }
+    `
+    const variables = {
+      input: {
+        name: 'yellow',
+      },
+    }
+
+    const data = await graphql(schema, mutation, undefined, undefined, variables)
+    expect(data).toEqual({
+      data: {
+        createColor: {
+          id: 'yellow',
+          name: 'yellow',
+        },
+      },
+    })
+  })
+
   it(`supports a body mapper`, async () => {

What would be your preferred way of mapping input fields to the request body and URL? There’s no body parameter in the createColor query above. It could be:

body: { name: "name" } // meaning body.name = input.name

or

body: "CreateColorMapper" // from mappers.CreateColorMapper

It is probably out of scope for this feature request but I think that body, query and provides could all accept mapper names. Functions are more flexible to map things.

Thanks for your lib btw 🙇

I do not want that the examples break without anyone noticing.

What to do:

• Extract the express instance into a separated file that exports it
• Test the exported express instance with supertest (https://github.com/visionmedia/supertest) and jest for some basic endpoint functionality.

How to do:

• Setup project (https://github.com/n1ru4l/graphql-schema-generator-rest#contribute)
• Add jest and supertest as a dependency to the examples
• Write some simple tests that prove that all features which are showcased in the example app are working

Related paths:

• https://github.com/n1ru4l/graphql-schema-generator-rest/tree/master/examples/express-complex
• https://github.com/n1ru4l/graphql-schema-generator-rest/tree/master/examples/express

Just to be extra confident about my code.

In the V2 breaking changes log, there is:

@rest(…, mapper: …) must be changed to @rest(…, responseMapper: …).

But in the code, there is no mention of a responseMapper option in the rest directive. My guess is that it is missing in the doc.

When status 204 (No Content), response.json(), throws SyntaxError: Unexpected end of JSON input. A temporary solution is to override the response .ok on the fetcher...

const fetcher = (url, options) =>
  fetch(url, options).then(response => {
    if (response.status === 204) results = { ...response, ok: false };
    return response;
  });

const schema = generateRestSchema({ typeDefs, fetcher });

This will be a breaking change 🙄

I will create a new branch for this and push it as a pre-release until the apollo-link-rest api becomes stable.

Current changes:

• Rename route param to path
• Replace provides param with @export directive
• fieldNameNormalizer Note: We have the more "powerful" mappers that can transform the whole request result body.
• Add a endpoint directive

Also nice to have:

• Update docs about differences between apollo-link-rest and apollo-schema-generator-rest combined with apollo-link-schema

Edit:

I am currently not working on this library. If anyone wants to bring it to a new level feel free to make proposals/open a PR.

Instead of supplying the schema string with lots of urls strings (that are mostly the same) it should be possible to shorten them. Also in case of a refactor there would be less code to change.

Idea:

new (object literal/string) option for function generateRestSchema: baseUri.

Case 1: baseUriis a string

import { generateRestSchema } from '@n1ru4l/graphql-schema-generator-rest'

generateRestSchema({ baseUri: `https://localhost:8080` })

Every route directive option that does not start with a scheme (e.g. https://, http:// is prefixed with the baseUri

Case 2: baseUri is a object literal:

import { generateRestSchema } from '@n1ru4l/graphql-schema-generator-rest'

generateRestSchema({ baseUri: {
  dogs: `https://localhost:8080`,
  cats: `https://localhost:8081`
} })

Every route directive option that does not start with a scheme (e.g. https://, http://) but has a uri directive option which matches a key of the baseUri option object is prefixed with the corresponding value.