fix(nested importing)

[SpaceK33z]

Previously only the files that were processed were kept in memory in a Set, to prevent circular dependencies. However, it can happen that a file gets imported two or more times, with different imports. To fix this, instead of only keeping track of the processed files, it now also keeps track of which specific imports from the processed files are used.

The new test I added illustrates this use-case. This might seem like a far stretch, but if you use Prisma and have separated files, e.g. "user.graphql" and "restaurant.graphql", and use each file to import specific types from "generated/prisma.graphql", you'll walk into this.

It cost me three hours to finally end up with a solution that is less code than before, so I'm very happy with that if I may say so 😅.

An explanation with examples

This is the use-case I'm fixing:

schema.graphql

# import Query.*, Mutation.*, * from "./restaurant.graphql"
# import Query.*, Mutation.*, * from "./user.graphql"

restaurant.graphql

# import Query.restaurant, Mutation.createRestaurant from "./prisma.graphql"

user.graphql

# import Query.user, Mutation.createUser from "./prisma.graphql"

Actual result

Only Query.restaurant and Mutation.createRestaurant get imported, Query.user and Mutation.createUser are ignored.

Expected result

Query.restaurant, Mutation.createRestaurant, Query.user and Mutation.createUser are imported.

[SpaceK33z]

Updated description to add a real-world use-case.

[SpaceK33z]

@divyenduz could you review this one? It is a bugfix so not a breaking change.

[divyenduz]

@SpaceK33z : Sure! thanks for the PR. On my list.