connectionPlugin in latest

[moverholt]

Hello!
I'm going through migration from Nexus Schema and I'm not able to get the connectionPlugin working.

I'm not sure if the connectionPlugin is not ready in the latest version or if I'm just doing something wrong.

Does anyone know if the connectionPlugin is working post migration from Nexus Schema?

Thanks!
P.S. Nexus is fantastic tool!

[danielle-cerisier]

Seems like a fair few plugins are still making their way over, but I haven't messed around with them.

I'm still using @nexus/schema with makeSchema and its working there.

[marceloverdijk]

The latest Nexus framework has the Connection plugin already bundles.
The basics are working but I encountered an issue extending the connections see here: graphql-nexus/nexus#450
Note the issue contains a link to a repo which you could check how to use the connection plugin.

[marceloverdijk]

See https://www.nexusjs.org/#/api/modules/main/exports/schema?id=tconnection

[jasonkuhrt]

Thanks for chiming in @marceloverdijk!

To add, you can use any schema plugin via schema.use but in this case, as mentioned, the connection plugin, it is already bundled with Nexus as t.connection.

[marceloverdijk]

@jasonkuhrt

I upgraded today from 0.23 to 0.24

  "dependencies": {
    "nexus": "^0.24.0",
    "nexus-plugin-prisma": "^0.10.0"
  },

but did t.connection('<name>', {}) change to t.connectionField('<name>', {}) ?

According to the docs it should be still t.connection

[jasonkuhrt]

but did t.connection('', {}) change to t.connectionField('', {}) ?

Nope, we did not change anything here. Still t.connection. t.connectionField is the default name on the schema plugin. You can ignore that.

[marceloverdijk]

Strange, upgrading to 0.24.1 seems to solve it and I can use t.connection again.