input types

[jexp]

Input types in the schema should be supported and passed into queries as maps that then can be deconstructed, for queries and fields and @cypher directives.

Input type for generated mutations is generated as part of those.

[jexp]

implict input types are already handled correctly e.g. in @cypher fields.

[jexp]

Perhaps split into two issues

first:

input Address(street: String, zip: Int)

filter(foo:Address)
-> Address is provided as "Map"

second:

also allow mutations (configurable) that take input types

input _CreateMovieInput(id:ID!, title: String, ....)
createMovie(movie: _CreateMovieInput)

there are already examples for that in the javascript version

[Andy2003]

I will add a new translator config to switch between following inputStyle-options:

1. TYPE this will generate one data-argument for the create, merge and update, where the type of the argument is the generated input type
2. PARAMS this will be the current behavior, where each filed of the target type is represented by an argument

The PARAMS-option will be default by now, but will be deprecated so in future releases we can switch to input-types

[jexp]

sounds good to me.

[jexp]

perhaps not data but aligned with the JS one enityName

[jexp]

Or check with @johnymontana

[Andy2003]

in @neo4j/graphql the input argument is called:

• input for creation and the input type is named <typeName>CreateInput
• update for mutation and the input type is named <typeName>UpdateInput, and all fields are optional