Some feedback from some lacking documentation regarding @cypher directive:

It is not clear in the doc how to add a param in a GraphQL query directly which then binds to a variable in a cypher query through the @cypher directive.

Add example and information of a cypher query with the @cyper directive doing a lot of matches with several properties from different nodes and relationships, then in order for GraphQL to parse it properly you need to create a typeDef which holds all that information of all the properties you want to return, and then return them as a map.

Authentication directive

READ
AGGREGATE
CREATE
UPDATE
DELETE
CREATE_RELATIONSHIP
DELETE_RELATIONSHIP
SUBSCRIBE

Authorization directive

filter:

READ
AGGREGATE
UPDATE
DELETE
CREATE_RELATIONSHIP
DELETE_RELATIONSHIP

validate:

READ
AGGREGATE
CREATE
UPDATE
DELETE
CREATE_RELATIONSHIP
DELETE_RELATIONSHIP

Originally posted by @mjfwebb in neo4j/graphql#4840 (comment)

Is your feature request related to a problem? Please describe.
Nowhere in the documentation is described how to work with logical operators (OR, AND), although it is implemented and works.

Describe the solution you'd like
The documentation for filtering should be extended by an example with OR or AND to make it easier for beginners.

For example, the following text could be inserted:

Filtering with logical operators
By using the OR or AND argument with a list of different filters, they can be logically related to each other. In the following example the User and 2 Posts can by retrieved by ID.

query {
    users {
        id
        name
        posts(where: {OR: [{ id: "2D297425-9BCF-4986-817F-F06EE0A1D9C7" }, { id: "SOME-OTHER-ID" }]}) {
            content
        }
    }
}

Is your feature request related to a problem? Please describe.
While working on a project in nestjs using Graphql and Neo4j I have come across a problem when I need to validate the inputs for the Qureries and Mutations. However if you're following the approach described in Nestjs' documents adding these validations (using class-validator) is quite straight forward.

import { MinLength, MaxLength } from 'class-validator';

export class CreatePostInput {
  @MinLength(3)
  @MaxLength(50)
  title: string;
}

Whereas it can't be done with the suggested Schema Types approach from Neo4j (as class-validator requires class schema).

interface Production {
    title: String!
    actors: [Actor!]! @declareRelationship
}

type Movie implements Production {
    title: String!
    actors: [Actor!]! @relationship(type: "ACTED_IN", direction: IN, properties: "ActedIn")
    runtime: Int!
}

Describe the solution you'd like
I am looking for way where it's possible to add Schemas using classes so that we can take full advantage of existing futures of Nestjs and develop the applications without these constraints

Is your feature request related to a problem? Please describe.

While upgrading from 1x to 3x It was not clear based on the guide that I MUST upgrade to ApolloServer 3, since graphql 16+ requires this. Additionally, I needed to go find the graphql changelog which I think just including for users in the guide would be easier.

I also suspect more users than you think will need to upgrade from 1x to 3x since the GRANDSTACK starter still installs 1x as you can see in their lock file.

Describe the solution you'd like

1. Add a mention at end of migration guide that ApolloServer 3.0 is required, maybe after this section.
2. Add a link to the graphql 16 changelog which included breaking changes and is something most upgraders will need to dig up manually.

Describe alternatives you've considered
None

Additional context
None

I searched the documentation for which erros are currently being thrown by neo4j/graphql, and under what circumstances. Unfortunately, there is currently no documentation for this.

I found the following errors in the code:

Neo4jGraphQLError

• Neo4jGraphQLForbiddenError
• Neo4jGraphQLAuthenticationError
• Neo4jGraphQLConstraintValidationError
• Neo4jGraphQLCypherBuilderError
• Neo4jGraphQLRelationshipValidationError

Most of these are actually self-explanatory, but what is the Neo4jGraphQLRelationshipValidationError for, for example?. Under what circumstances is this error triggered? How should this error be handled?