De-duplicate relationship projection when not using connection API

[mjfwebb]

Description

This PR introduces a change in the result projection where there are multiple relationships between two nodes.

In the case of using the connection API then multiple relationships will still be represented, as there is the ability to select the relationship properties. In the non-connection API case, the duplicate results will only return distinct results.

For example:

Data set:

CREATE (m:Movie} {title: "Movie One"})
CREATE (a:Actor} {name: "Actor One"})
CREATE (a)-[:ACTED_IN {role: "Role One"}]->(m)
CREATE (a)-[:ACTED_IN {role: "Role Two"}]->(m)

Connection API (actorsConnection):

query {
    movies {
        title
        actorsConnection {
            edges {
                node {
                    name
                }
                properties {
                    role
                }
            }
        }
    }
}

With the results:

movies: [
    {
        title: "Movie One",
        actorsConnection: {
            edges: expect.toIncludeSameMembers([
                {
                    node: {
                        name: "Actor One",
                    },
                    properties: {
                        role: "Role One",
                    },
                },
                {
                    node: {
                        name: "Actor One",
                    },
                    properties: {
                        role: "Role Two",
                    },
                },
            ]),
        },
    },
],

Non-connection API (actors):

query {
    movies {
        title
        actors {
            name
        }
    }
}

With the results:

movies: [
    {
        title: "Movie One",
        actors: [
            {
                name: "Actor One",
            },
        ],
    },
],

Complexity

Low

[changeset-bot]

🦋 Changeset detected

Latest commit: d48ea32

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@neo4j/graphql	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR