angrykoala

Yeah, that would be the rough idea. I don't think the second snippet will work, as the source is not valid GraphQL. #1962 (and the related #2265) is something that...

Hi @andreloeffelmann I'll close this issue now, as the first two items have been addressed already and the third one is covered by #2265 Feel free to comment if I...

Hi @andreloeffelmann `totalCount` is generally intended to be used as part of a paginated result. For the case you mention, try using [Aggregation Operations](https://neo4j.com/docs/graphql/current/queries-aggregations/aggregations/#_aggregation_fields) which should not return the edges,...

Hi @andreloeffelmann Sorry, my bad, this last query has a bug that causes that extra edges to be returned. Until that is fixed you can use the deprecated aggregate queries...

This issue is now fixed for the queries such as: ```graphql normsConnection { aggregate { count { nodes } } } ``` It will be available on the next 6.x...

Hi @andreloeffelmann Would it be possible to apply the workaround in #6206 ? The underlying cause of #6206 is a variable name conflict, which may affect other queries, not only...

Hi @andreloeffelmann Yeah, I'll be looking at this one as well, I'm first checking #6206 as its root cause will cause other issues, not just in aggregation. I'll come back...

Hi @andreloeffelmann #6206 is quite tricky, as it may cause unexpected breaking changes if fixed for your use case. In the meantime, I've made a patch to fix this performance...

Hi @CharlieDigital This is a neat idea, it could also be applied to other places such as `variable.property()`

Hi @aleffert thanks for the reference, that's very helpful I'm all for adding options to improve type safety, although that can be tricky in such a low level query builder...