Jason Kuhrt

> $name and $description cannot be generated for input types Hm, I think I disagree. We can have default values for both that users can opt into. For the description...

Oh that's interesting too. I tend toward favouring static where appropriate, since more data oriented that way. I also wonder if we'd find another use-case for field parameters later (e.g....

For BigInt lets link to https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt.

Hey @nikolasburk can you help with: `Link pris.ly/d/nexus-prisma doesn't work`? Hey @Jolg42 can you help with `Wrong location, should be after the generated nexus prisma to ...`?

@nikolasburk I need to setup that shortlink to point to this repo's [README](https://github.com/prisma/nexus-prisma/blob/main/README.md). @Jolg42 No, Instead of this: ``` You can now start using Nexus Prisma in your code. Reference:...

@Jolg42 this is the code https://github.com/prisma/nexus-prisma/blob/feat/allow-custom-context-property-name/src/cli/nexus-prisma.ts#L29-L36 where the log output I am writting is. I assume I'm putting it in the wrong place.

@Jolg42 I'm talking about the Nexus Prisma log. Sorry my example above was broken. Fixed now.

> BTW: adding the following eslint rule would catch this kind of error: @typescript-eslint/strict-boolean-expressions PR welcome

@garth I'll try to review the docs and see if there are any missing steps.

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