Miguel Oller

@hwillson, this is still a problem using `@apollo/client@latest` and can be easily seen by checking the reproduction sandbox provided. Would it be possible to check the issue has been fixed...

No problem. Thanks for re-opening the issue!

@brainkim, the use-case is to avoid having to specify all fields in GraphQL mutations that create new resources. There's a very insidious bug, which might not actually be a bug...

@erydo, that's a very good point! I do agree that having the errors invalidate the entire connection is undesirable. Perhaps the non-nullability suggestions for nodes or edges aren't very good....

@iDuuck, that looks great! Thanks for taking the initiative 😄 I'm not sure how responsive @rpl is to PRs but I'm sure it would be helpful if you submit one...

What about `restEndTuple`? For example: ```es6 type restEndTuple = [void, ...string]; ``` In my case this is useful because I'm representing a heap using an array and while every element...

Sounds good! Thank you!

@dan852, thanks for sharing the workaround! If you want to select all columns, something like this worked for me to get the right SQL: ```ts db .select({ row: sql`* distinct...

> I guess it's more a bug for `.values({})` syntax. We should fix this one Yeah, makes sense. So something like this? ```ts db.insert('table').values().returning().toSQL() // { sql 'insert into "table"...

> Prior discussion: #14357 Thanks for pointing out that discussion @eps1lon. It seems that the visual building case is a common use case. That being said, that issue seems to...