Søren Bramer Schmidt

@Discordius I agree that we should be careful no to impose any mongo-isms on the architecture if the goal is to support many databases. That said, I actually think the...

One additional aspect is performance. We expose two versions of our api - one that is relay compatible and one that is human readable. For one particular query the relay...

Even if relay doesn't add support, it would still make it possible to have just one relay compliant api and use relay for most things, but fall back to plain...

I understand your proposal is aiming to improve the spec. But I just wanted to point out that supporting "nested mutations" is entirely possible within the existing GraphQL spec. Here's...

@IvanGoncharov Thanks for the detailed writeup. Do you think it would be more practical to introduce Unicode only for Enum names?

While GraphQL does not support union input types, a single input element is actually coerced into a single item list, so in this case we don't need a union type...

Thanks Emi! ## 1. createdAt and updatedAt createdAt and updatedAt are specific to the current version of Prisma and should probably not be included in OpenCRUD at all. ## 2....

@GromNaN - I agree that we should move towards being less opinionated about the existence of updatedAt and createdAt fields 👍 Separately - I just provided a comment on the...

Would we be able to improve this experience through the VS Code plug-in? Cc @carmenberndt

Thanks @Trellian - some good thoughts! First - I have corrected the typo. About the M2M join table: A core design goal of Graphcool is to enable pain-free schema migrations...