Andre Löffelmann

Results 12 issues of Andre Löffelmann

### Describe the bug Let's assume we have a Grid instance with: `grid.setRowsDraggable(true)` All columns of the grid are then - as expected - draggable. Now hide a column by...

bug

**Is your feature request related to a problem? Please describe.** We have type properties that are not related to a node property in neo4j but rather are "auto-generated" via a...

feature request

**Describe the bug** The `@populatedBy` directive does not work if the field the directive is declared for has the `DateTime` datatype. The callback function never gets called. **Type definitions** ````graphql...

feature request

**Is your feature request related to a problem? Please describe.** When filtering for fields of type `String` in queries the passed filter values are compared case-sensitive to the database values,...

feature request

**Describe the bug** When using the coalesce directive on a field, it is not working. The given default value is not returned. If the field is marked as non-nullable, an...

feature request
small

## Issue Description If an input field for a mutation is e.g. of `DateTime` type, the generated GraphQL mutation contains the stringified datetime not in escaped strings which leads to...

bug

### Type definitions ```GraphQL type Cat { chases: Mouse! @relationship(type: "CAT_CHASES_MOUSE", direction: OUT, aggregate:false) } type Mouse { name: String! @unique eats: Cheese! @relationship(type: "MOUSE_EATS_CHEESE", direction: OUT, aggregate:false) } type...

feature request

**Describe the bug** When defining filters via the `@authorization` directive, these filters are not rendered as `WHERE` clauses inside subqueries which match/reference on the (root)-node for which these filters are...

enhancement

**Describe the bug** When declaring a field of type `list` of `enum`, the generated `*EnumValueListEnumScalarMutations` input types for update mutations declare both `set` and `push` fields as required. **Type definitions**...

confirmed
bug

**Describe the bug** Queries for aggregate counts (within connections) produce GraphQL errors for _some_ GraphQL types. It's _some_ because I cannot detect a pattern determining when it works and when...

confirmed
bug
breaking