Ville Saukkonen

I would prefer inner join to return tuples instead of merging. That way no data is lost and the api would bend to more use cases. Or alternatively allow the...

@CrossEye do you think it could be a good time to rename `innerJoin` (back) to `intersectionWith` and (re)implement `innerJoin` so that either tuples are returned or then the `innerJoin` would...

This is what I ended up doing for now: ``` import { indexBy, prop, // @ts-ignore innerJoin, eqProps } from 'ramda'; export const betterInnerJoin = ( key: string, mangle: (T1,...

Something like this happens to me too. The error message is not very helpful to pinpoint what's going on. This happened when I made some drastic changes to my prisma...

Hmm yeah, something like `t.private.field(SomeObject.slug);` could work. Or then in the resolver: ``` t.string("url", { requires: [t.field(SomeObject.slug)], resolve(root) { return `www.url.com/${root.slug}`; }, }); ``` Both are somewhat verbose, but would...

@jasonkuhrt would not want to push this, but this is maybe the biggest issue type wise in nexus at the moment. The types of `root` variable are virtually always wrong.

Maybe something like: ```ts type InputType = { id: string; name: string, slug: string; } export const SomeObjectType = objectType({ name: SomeObject.$name, description: SomeObject.$description, definition(t) { t.field(SomeObject.id); t.field(SomeObject.name); t.string("url", {...

I'd like to be able to just click the value which would open the text input.

I believe this is essentially the same problem: https://github.com/CodetrixStudio/CapacitorGoogleAuth/issues/126

Getting the same error in jest tests and there is no good workaround.