Darrell Warde

We have initial designs for a new directive which support more complex relationship paths in a read-only manner, but don't intend to add this functionality to the `@relationship` directive.

As you've seen, feature development is well underway! They are currently hidden under an `experimental` flag that we've introduced, so not ready for production use yet, but you can play...

Out of interest, what should the behaviour be here in your opinion? I ask because `null` and `undefined` are obviously two very different argument values - the former usually being...

I agree that the current behaviour is open to mistakes being made - an inconvenience in development, but a potential nightmare in production. I would definitely say two options here:...

That's certainly an interesting observation that arguments with value undefined don't even reach the resolver - I wonder if they're in the ResolveInfo object? Nice example. 🏆 Perhaps there is...

> That seems sensible at first blush. Is it as simple as "An empty input is an invalid input." Are there any instances where an empty input would be desirable?...

Closing this because it seems as though the directive is there in the output and should work as advertised - perhaps an issue with the cost calculation library itself?

Closing as covered by #2867.

I think we need to be realistic here about the complexity of custom Cypher queries that we'll ever be able to support. If this was returning a node and that...

> Any update on this? It's quite a problematic error, and the alternative suggested doesn't work when combining with `allowUnauthenticated` since the `jwt` is not defined and therefore so is...