- Translating fragments on interface types
- Initial support for union types
- Generated pagination for union type fields
- Bump graphql-auth-directives version
- Use latest APOC release in integration tests
- Fix #295 Querying interface @relation fields with non-unique relationship names
- Update driver user agent
- Fix #361 Merge node should add interface label
- Fix #349 Interfaces with no scalar fields generate invalid schemas
Note: Multi-database support is not exposed via neo4j-graphql.js in this release, only the default database can be used with neo4j-graphql.js. Multi-database support will be addressed in a future release.
- Initial spatial support using Point type
- Spatial filters
- Fixes for generated schema type and default config
- Interface handling: generate queries for interface types + FRAGMENT_TYPE fix
- Fixes for incorrect and non-existing hasScope directives
- Duplicate query argument fix
- Schema augmentation refactor
- Carry non-fragment fields into the result for a fragment
- Integration test updates
- Fix for incorrect behavior in filters
- Fix bug where Camel/Pascal cased variables were broken in filters
- add FRAGMENT_TYPE when customQuery and customMutation resolve interfaces
- fix: do not assign undefined to x_filter keys
- Fix: Handle multiple inline fragments
- Initial support for federated schema
- Support for multi-tenancy using additional labels
- Initial support for generated filter argument
- Don't include
SKIP
clause in the generated Cypher query if nooffset
parameter is specified. - Dependency updates.
- Fix for querying interface type when no fragment is specified
- Fix for
@cypher
directive input type argument parameters
- Support for authorization schema directives via graphql-auth-directives
- Pass context data to Cypher params
- Fix for scalar payloads on Cypher directive fields
- Fix for input type arguments on Cypher directive fields
- Fixes nested ordering
- Ordering by temporal type
- Support ordering by enum type
- Fix call stack size exceeded with large schemas
- Fix customer Cypher query on root query field with no arguments throws error
- Support arrays of orderBy arguments
- Ignoring fields with neo4j_ignore directive
- Don't exclude first, offset, orderBy params from Cypher directives
- Use Neo4j driver transaction functions
- Support for temporal fields on relationships
- Scalar and temporal list fields
- Fix Adding ! to a DateTime Field, throws an error
- Support for reflexive relationship types. #125
- Fix #113 Don't drop non-Query/Mutation resolvers passed into makeAugmentedExecutableSchema
- Fix #124 Basic schema with non nullable property gives error when calling mutation
- return better error message in case name or direction haven't been specified into the directive
- Support for relation types with managed directional fields from and to, along with an optional @relation type directive
- Auto-generate value for ID field if not specified in create mutation
- Include custom scalars in the arguments of generated mutations
- Augment schema refactor #84
- Add update, delete, and remove relationship mutations
- Update debug NPM script
- Add code coverage reporting
- add top level orderBy tests