angrykoala

Right now, GDS is out of scope for the Cypher Builder, we've been discussing whether or not we should add direct support for these, but considering all these functions and...

Hi @jroith Thanks for sending this for reference. Just to make it a bit easier to follow could you sent me an example of a GraphQL query and the Cypher...

Hi @jroith As this is more of a reference to make performance improvements I changed this PR to a draft, as it is not intended to be merged Thanks again...

Hi. I've been looking into this for version 7, in this version we have changed our filters, giving us more flexibility to add case insensitive filters without incurring into a...

There are some details of the API that are still pending discussion, the PR #6250 needs to be merged for this issue to be closed

Hi @andreloeffelmann We have discussed the different API options and the features has been merged. Case insensitive filters will be available in the next 7.x release soon. Apologies for the...

Hi @andreloeffelmann I'm not able to reproduce this The type definitions: ```graphql type MediaAssetClass @node { id: String } ``` On version 6.6.1 of the graphql library are generating for...

Thanks for the extra info, yeah, I can confirm it is also happening on version 7 with the following minimal typeDefs: ```graphql type MediaAsset @node @subscription(events: []) { classes: [MediaAssetClass!]!...

I think the problem is some conflict between `MediaAssetClass` and `MediaAsset.classes` in the generated types, as renaming either the `classes` property or the `MediaAssetClass` type seems to fix it

Same situation, `MediaAsset.versions` conflicts with `MediaAssetVersion` This may not be easy to fix quickly, as we need to change the names of the generated schema, which may have unwanted ramifications....