Nexus-plugin-prisma: Subscriptions are not supported yet with `t.prismaFields`

[Weakky]

TODO

• Waiting for https://github.com/prisma/nexus/issues/21 to land
• Resolve subscription types
• Generate proper typings for subscription types

[williamluke4]

@Weakky Anything I can do to help here?

[Weakky]

Hey !

PR are always appreciated, feel free to dig into the codebase and create a PR if you feel like so !

As far as I can tell, there are two things to change:

• The generated resolvers needs to support subscriptions (atm, it just throws)
• And generate the correct types in nexus-prisma-generate

[Weakky]

Update: This needs to be rolled out first https://github.com/prisma/nexus/issues/21

[nevescode]

@Weakky prisma/nexus#21 is now closed!
More details on PR: https://github.com/prisma/nexus/pull/66
I'm very anxious about subscriptions with nexus-prisma.
I'll try to dig out in the code this weekend to propose a PR. Thanks for the good work!

[Weakky]

@nevescode That's amazing! If you need any help, feel free to DM me on the Prisma slack @weakky 🙏

[kolengri]

Hi any news about this? 😢

[Weakky]

Hey everyone,

While we haven't implemented subscriptions yet, it's important to mention that subscriptions should already work nonetheless with nexus if you implement the resolvers yourself with subscriptionField().

What doesn't work yet are the automatic resolvers when using t.prismaFields([])

[BjoernRave]

hey, may I ask if you/somebody knows when to expect this feature?

[mahapo]

+1

[sangqle]

Awesome. Hope as soon as possible.
Have a good day.

[kolengri]

So is topic dead? :(

[mahapo]

Should be fixed with this https://github.com/prisma/nexus-prisma/releases/tag/v0.3.7

[pierreyves-lebrun]

Apologies if I am missing something but isn’t that rather a workaround?

I think subscription via t.prismaFields() syntax is what we are all after.