Benedikt Franke

As i made the switch, i had a few hundred auto-generated types. I was able to simplify the code generation massively and quickly add new capabilities to the queries. The...

I generated everything, including models, from an existing database schema. While Lighthouse is centered around Eloquent, it is not limited to it. You can define custom resolvers anytime you need...

The issue with the current scalar types is that they cover up errors. For example, the rule to check if an input field is a boolean does not work in...

I recommend using https://github.com/nuwave/lighthouse instead. It supports pagination out of the box, without writing any code https://lighthouse-php.netlify.com/docs/next/directives.html#paginate

> JWTs are usually user input and I believe it's responsibility of the users of this library to rely on the interface and verify they have the expected type of...

The library currently has `(string $token): Token)` and `(string $probablyUnencryptedToken, SignedWith $signedWith, ValidAt $validAt, Constraint ...$constraints): UnencryptedToken`. It is clear to me that there is a gap between those, and...

@Chrisdowson I was willing to include this example with a few minor tweaks, if you are still up for it.

I think @k0ka has outlined quite nicely what would be necessary to safely recognize when validation for a query should lead to identical results. If we get this part right,...

The variables influence the result, but they are not relevant for basic document validation. See https://github.com/webonyx/graphql-php/blob/7a78690e99548de8155f605772eecf615329ee16/src/GraphQL.php#L143 - variables are not passed to `DocumentValidator::validate()`.

> As I see they are passed into QueryComplexity ? Right. I think we can check if `lighthouse.security.max_query_complexity` is enabled, and include the variables in the hash based on that....