Subscription and service level resolver

[palpinter]

My problem is when I define resolvers in settings with graphql, resolvers works as expected when I call a query. But when I call subscriptions resolvers do not work.

This is the example definition:

graphql: {
    type: [
        Employee,
        EmployeeList,
        Address,
        Phone,
        Email,
        AddressInput,
        PhoneInput,
        EmailInput,
    ],
    resolvers: {
        Employee: {
            gender: {
                action: "genders.read",
                rootParams: {
                    gender: "code",
                },
            },
            maritalStatus: {
                action: "maritalStatuses.read",
                rootParams: {
                    maritalStatus: "code",
                },
            },
        },
        Address: {
            streetType: {
                action: "streetTypes.read",
                rootParams: {
                    streetType: "code",
                },
            },
        },
    },
},

Do I need to define other resolvers for subscriptions? I haven't found any example of using resolvers with subscriptions.

This works in the http://localhost:3000/graphql:

query {
  employee(code: "0000000017") {
    code
    gender {
      code
    }
  }
}

But this doesn't:

subscriptions {
  employee(code: "0000000017") {
    code
    gender {
      code
    }
  }
}

Sorry but I don't understand.
Thx

[shawnmcknight]

Without seeing the rest of your service definition its hard to figure out what's going on here. Can you make a repo with your services in it to give the full picture?

[palpinter]

Hi,

Thanks for your fast answer.
This is the repo:
https://github.com/palpinter/moleculer-apollo-demo

The services/employees.service.js file contains the relevant code.

[palpinter]

Sorry for faulty closing. The question is open.

[palpinter]

Hi,

I dont understand well your code, but I have changed the service.js line 313 from:

this.broker.call(actionName, { ...params, payload }, ctx),

to

this.broker.call(actionName, params)

So it is works now in playground.
But I not able to use it from React Apollo client on websocket link. It drops error:

{ "errors": [ { "message": "Cannot read property 'call' of undefined", "locations": [ { "line": 10, "column": 7 } ], "path": [ "employee", "gender" ], "extensions": { "code": "INTERNAL_SERVER_ERROR" } } ], "data": { "employee": null } }

It means for me, that the resolver doesn't work.
Thx
P.

[icebob]

@Hugome maybe could you help with it?

[Hugome]

The path in the error is "employee.gender", which mean that the resolution of this field has an error.

{
  "errors": [
    {
      "message": "Cannot read property 'call' of undefined",
      "locations": [
        {
          "line": 4,
          "column": 5
        }
      ],
      "path": [
        "employee",
        "gender"
      ],
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR"
      }
    }
  ],
  "data": {
    "employee": null
  }
}

With a little of digging the context.ctx in src/service.js#200 is undefined, because it's not defined in case of a ws connection src/service.js#576.
I've open a PR to propose a solution for this case : #73

[palpinter]

Thank you very much @Hugome!
It works with my change:
from

this.broker.call(actionName, { ...params, payload }, ctx),

to

this.broker.call(actionName, params)

But not without this.

Once more thank you.
P.