David Blass

@jasonkuhrt @Weakky There's a lot here, so to make sure I have enough time to finish up stage 1, I'm just going to list my first couple thoughts: 1. [This...

My thoughts on this are still summarized well by [my previous comment](https://github.com/prisma-labs/nexus-prisma/pull/566#issuecomment-579457507). I tried using ```creatable/connectable``` and it just didn't click. I feel confident that having a way to opt...

@maartenraes Thanks so much for taking the time to write this up. It's awesome to see others interested in ```nexus-prisma```'s unsolved problems and that type of input (no pun intended...

@maartenraes I've seen a nested update like that so I'm not totally sure how it would work, however ```relateBy``` only affects inputTypes with two fields, ```create``` and ```connect```, by replacing...

@maartenraes I love the idea of having a fluid API for performing multiple nested relations. I'd worry a bit that it's not obvious what's going on with blogs at a...

@Weakky @jasonkuhrt Thanks for the work you've done on this. I think there is some really interesting discussion to be had around, for example, type safety for return values of...

@jasonkuhrt The original implementation of this feature was ```upfilterKey```, which did exactly what you're describing: allowed the user to pass in the name of any field they want "compacted," provided...

@jasonkuhrt Thanks for your flexibility. ```upfilterKey``` was originally a string, not a boolean. The example I gave in my first comment on https://github.com/prisma-labs/nexus-prisma/pull/566 was this: ```t.crud.createOneTest({upfilterKey: "create"})``` > ```ts >...

@jasonkuhrt > compact will only ever make sense when fields in the layer (speaking as generic as possible) are reduced to exactly 1 Yes, that is what I've been trying...

@RyanCavanaugh Is this not worth patching into TS 5.5? Given how easy this is to repro, I'd assume this would occur often in the wild. Issues like this that are...