Benedikt Franke

@wimski that would run `@guard` twice. I think we should enhance the field middleware configuration to allow defining a default order for field middleware. That would allow interleaving optional field...

I am not looking to implement this myself, but would assist in reviewing a pull request and include it in Lighthouse.

Thank you for your well-written proposal. Given we abstracted out the tricky bits of the complex where conditions into https://github.com/nuwave/lighthouse/blob/master/src/WhereConditions/WhereConditionsBaseDirective.php, adding another directive that is essentially a variant of `@whereHasConditions`...

First, I suggest to implement the trivial case without `@select`: ```graphql { posts { id title } } ``` ```sql select id, title from posts; ``` Next, consider the implementation...

Also, see https://github.com/nuwave/lighthouse/pull/1253

A partial solution is better than no solution at all, if there are shortcomings we can document them and offer users the choice. Let's just make sure that whatever is...

Validation has been completely revamped, you can check out the latest `master` and see how your desired change might fit in there. Open for PR's.

I agree that nested deletes should be limited to existing relations and am open to PR's. Here is the responsible code https://github.com/nuwave/lighthouse/blob/301930b356faa63da681d564cbef41c7d312f2aa/src/Execution/Arguments/NestedOneToMany.php#L32-L36 Off the top of my head, i can...

> Any update on this? The last update was [this comment](https://github.com/nuwave/lighthouse/issues/1400#issuecomment-638270338). Are you not able to see the comment history? Unless someone decides to put in the work and provide...

Lighthouse has no restrictions in place for any kind of relation. Every possible combination of relation and nested operation where ids are passed by the user is affected by this.