Enum imported form nexus-prisma doesn't have autocomplete value

[sooxt98]

Currently need to import twice from @prisma/client and nexus-prisma, one for GraphQL schema another for values

[jasonkuhrt]

I'm closing this as a misunderstanding of what nexus-prisma is.

TransactionStatus from nexus-prisma is supposed to be a Nexus enum.

https://nexus.prisma.io/features#project-enums

[sooxt98]

@jasonkuhrt sorry, i think im not describe it clearly, here's my question

Is is possible to expose enum property for autocomplete directly via nexus-prisma generated interface?
Just like the example shown below, which i added manually

[jasonkuhrt]

@sooxt98 I'll need some convincing for this because its a significantly different use-case than what nexus-prisma is trying to give you. I get the appeal at first but as an API it doesn't make much sense.

[sooxt98]

@jasonkuhrt its easily to get confused with two different import and need another name just for enumType, why not just combine like the User interface from nexus-prisma

Pros:

• it works more naturally like Prisma ( works as it should be
• reduce confusion for new user
• reduce need for extra import

Doesnt it look nicer and simpler to have one import instead of two?

I like nexus-prisma alot, i think this simple touch could make developer life alot easier by providing consistency, i cant think of any cons for doing this ,thanks 💖

[jasonkuhrt]

The con of this is that its a enum use-case served by a much larger and unrelated source of data. So many example where the fit is awkward.

1. Hovering over TransactionStatus enum should show a dead simple focused type on that enum, nothing to do with Nexus.
2. Use that enum should not requiring dragging in whatever NP has generated
3. User should be able to stop using NP and have those enum callsites keep working

I'm against this on principal as it trades API concern/coherence for convenience.

I am definitely onboard with you about the problem, but not this solution yet.

If you could easily import NP in a name-spaced way, perhaps that would help.

[sooxt98]

@jasonkuhrt yea It's kinda anti-pattern, maybe it could be an extra optional option for those who needs to write cleaner code? The nexus-prisma hovering card do show the enum types but with some weird typing above, however i do think the np one's is looking much cleaner

maybe i should find a way to make it NP-less

nexus-prisma:

prisma: