Leonardo Losoviz

The bug happens only when adding "query" at the beginning of the query: ```graphql query { user @include(if:false) { name } } ``` This query had no issue: ```graphql {...

Hi @dolevf that would be awesome, thanks! (Btw, I loved your presentation!) I'll accept your help. I still need to protect the server by query complexity analysis, though, and I...

All packages are currently on level 5. Keep working it up!

Because the typed property will be the type class and not its resolver, we need a way to correlate the type class and its type resolver class. Eg: a user...

Related to: - #1457

After fixing, those sections of the code that must re-enabled, are those with this PHPDoc: ```php // @see https://github.com/leoloso/PoP/issues/1614 ``` or: ```php /** * @see https://github.com/leoloso/PoP/issues/1614 */ ```

It can be done already, you just have to create a matrix in GitHub Actions, iterating over the PHP versions and creating the release for each (the PHP version to...

Actually, reloading the GraphiQL client still makes sense when changing the Schema configuration, so that the docs in the GraphiQL explorer will be updated.

Reloading the client may be possible with GraphiQL `v2.0`.

The issue started happening after [this change](https://github.com/leoloso/PoP/commit/79e0e581de5bc06e872a6b10f3d639d6e25f97be) in `layers/API/packages/api-mirrorquery/src/DataStructureFormatters/MirrorQueryDataStructureFormatter.php`: ```diff - // Watch out! If the property has already been loaded from a previous iteration, in some cases it can...