GraphQL starter duplicates classpath when jar is soft symlinked about graphql-spring-boot HOT 3 OPEN

If it’s on the classpath (through a symlink or directly) you’d want to be able to load graphql schemas from it as well I’d say. Can you provide an example of your setup how to reproduce it? Especially interested in which jars contain the graphqls resources and which the accompanying classes.

Apparently in your case the file that’s symlinked contains graphqls resources you want to ignore?

There’s a change in the upcoming release where you can configure the schema pattern for finding schemas to load from the class path. Would that be a solution for your situation?

from graphql-spring-boot.

@snowe2010 Is this still an issue, or not anymore with the latest release and can we close it? See also my previous comment.

from graphql-spring-boot.

Sorry, I forgot to respond to this message. Github doesn't make it easy to remember to do things later.

If it’s on the classpath (through a symlink or directly) you’d want to be able to load graphql schemas from it as well I’d say. Can you provide an example of your setup how to reproduce it? Especially interested in which jars contain the graphqls resources and which the accompanying classes.

I don't really care if it's loading symlinks, but that appeared to be the issue that graphql was encountering when using the extend type syntax. I can't provide a code example, but I could provide the architecture, but I don't think that would be much help.
The issue we encountered was that we have many many schemas, and if you need to extend one then you try to use the extend type notation and get the above error.

from graphql-spring-boot.