angrykoala comments

Results 155 comments of


                                            angrykoala

rfc/unwind-create

Complex examples added, this should be fully pitched now

Cypher queries are not executed and return null for nested results in lists

@darrellwarde The wrapping functionality is not used [here](https://github.com/neo4j/graphql/blob/23eba320d0cebeb37f212acb0be5eee978043d0a/packages/graphql/src/schema/resolvers/cypher.ts#L182) We could refactor the resolver to start using `wrapInApocRunFirstColumn` or, for a quicker workaround, use the `escapeQuery` utility on the statement directly.

allow rule on @auth is not throwing FORBIDDEN error when rule is not satisfied on CREATE mutation

Hi @Karthikeyan-Vijayan I'm afraid that to faithfully reproduce this problem, I need to know more context regarding the users and posts in the database I noticed that both mutations are...

allow rule on @auth is not throwing FORBIDDEN error when rule is not satisfied on CREATE mutation

Thanks @Karthikeyan-Vijayan ! If you could edit the original comment to fix mutation 2 that would be great

@auth directive and combining where with roles

Hi @pandemosth Just as you mention, the problem here is that roles are not specified in each rule, at the moment, this falls right into a redesign on how the...

Using alias for an autogenerated <connection> relation in a GraphQL query leads to an invalid cypher query generation when used nested in the GraphQL query

As mentioned by @darrellwarde, connections were completely overhauled in #2053 in the last release (3.8.0), Currently, the error is reproducible but with the following message: ``` Neo4jError: Variable `containsMaterialConnection` not...

Using alias for an autogenerated <connection> relation in a GraphQL query leads to an invalid cypher query generation when used nested in the GraphQL query

This has been fixed in #2098

angrykoala

rfc/unwind-create

Cypher queries are not executed and return null for nested results in lists

allow rule on @auth is not throwing FORBIDDEN error when rule is not satisfied on CREATE mutation

allow rule on @auth is not throwing FORBIDDEN error when rule is not satisfied on CREATE mutation

@auth directive and combining where with roles

Using alias for an autogenerated <connection> relation in a GraphQL query leads to an invalid cypher query generation when used nested in the GraphQL query

Using alias for an autogenerated <connection> relation in a GraphQL query leads to an invalid cypher query generation when used nested in the GraphQL query

Duplicate Nodes Created with Nested 'Connect' when using Interfaces

Logging of the objects (or object IDs) created, updated or deleted during a mutation.

Refactor: Use Subqueries