neo4j-graphql-js

neo4j-graphql-js copied to clipboard

Unintended security issues with query filter params and schema augmentation

7

# Problem So we have a graphql type `User` like this: ```graphql type User { id: ID! name: String email: String! password: String! } ``` If you do schema augmentation,...

roschaefer

[BUG] Error when using required for DateTime on mutations

1

Hello, the parse of required `DateTime` in mutations doesn't work like when it's not required, when i do this: ``` type Mutation { CreateMessage( id: String = "" text: String!...

Crodaycat

[BUG] Filtering in generated queries get erros

17

When i try to filter with any field (no matter the type) it throws an error: Query: ``` query { Chat (filter: {roomNumber: 10}) { id roomNumber } } ```...

Crodaycat

Any possibility of allowing multiple data sources soon?

6

I noticed it was in the goals, I'm beginning a new project and would love to consider neo4j rather than mongodb but don't want to have to create separate APIs...

partounian

CLI for utility type tasks

2

As suggested in #269, a command line interface for executing utility tasks could be helpful for executing some one-off tasks, such as: 1. writing augmented type definitions to file 1....

johnymontana

Cannot create custom resolvers without @relation

7

I am making a photo gallery site, and photo urls are generated on the server and not managed by the neo4j database. This is currently my typedefs: ```graphql type PhotoURL...

viktorstrate

Only first result returned for custom query / resolver

2

I have this bizarre behaviour whereby I only get the first result returned for a query. I assumed I am making some mistake but I really can't figure it out....

infornite

Nested fields for Cypher queries

3

Given this schema: ``` type Club { _id: Long! id: String! image: String name: String! in_league: League @relation(name: "IN_LEAGUE", direction: "OUT") transfers_from_club: [Transfer] @relation(name: "FROM_CLUB", direction: "IN") transfers_to_club: [Transfer] @relation(name:...

mneedham

Inconsistent handling of cypher parameters in cypher tests

1

Discussion from PR #255: > test/helpers/cypherTestHelpers.js const checkCypherMutation = (object, params, ctx, resolveInfo) => { const [query, queryParams] = cypherMutation(params, ctx, resolveInfo); t.is(query, expectedCypherQuery); t.deepEqual(queryParams, expectedCypherParams); @roschaefer roschaefer on May...

johnymontana

@relation on type does not respect non-nullable marks

1

Unfortunately these two definitions do not produce the same schema: ```sdl type A { uuid: ID! bs: [B!]! @relation(name: "HAS_B", direction: OUT) } type B { uuid: ID! as: [A!]!...

smajl