contextType path starts with "#"

[sarink]

Node supports subpath imports as long as the import begins with #. However, the way that contextType works is by looking for an exported variable name after the #

That means if your context file is located in an aliased subpath, ie "#api/src/context#Context", the generated types will have an import which cannot be resolved.

Suggestion: Consider using a different character, since Node has already claimed # in import paths

[productdevbook]

same problem contextType: '#pergel-graphql#PergelGraphQLContext',

[dotansimha]

I assume the only solution here is allowing to escape # with something like \\#?
@saihaj what do you think?

[productdevbook]

Can we please resolve this? It's getting in the way. :( Thank you

[productdevbook]

enumValues: {
  RoleStatus: '#changeName/server/drizzle/schema#RoleStatus',
}

enumValues same problem

[saihaj]

@productdevbook do you want to send a PR with a failing test case and a potential fix?

[productdevbook]

@productdevbook do you want to send a PR with a failing test case and a potential fix?

I wanted to, but I couldn't find where it was.

[productdevbook]

@dotansimha @saihaj i am send pr please check.