You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Interfaces - having multiple interfaces in schema generates errors on startup #45
Caused by: com.coxautodev.graphql.tools.SchemaClassScannerError: Error creating bimap of type => class
at com.coxautodev.graphql.tools.SchemaClassScanner.validateAndCreateParser(SchemaClassScanner.kt:141) ~[graphql-java-tools-3.2.1.jar:na]
at com.coxautodev.graphql.tools.SchemaClassScanner.scanForClasses(SchemaClassScanner.kt:124) ~[graphql-java-tools-3.2.1.jar:na]
Caused by: java.lang.IllegalArgumentException: value already present: null
at com.google.common.collect.HashBiMap.put(HashBiMap.java:287) ~[guava-21.0.jar:na]
at com.google.common.collect.HashBiMap.put(HashBiMap.java:262) ~[guava-21.0.jar:na]
at com.coxautodev.graphql.tools.SchemaClassScanner.validateAndCreateParser(SchemaClassScanner.kt:138) ~[graphql-java-tools-3.2.1.jar:na]
... 81 common frames omitted
I think I know what's causing this, and a workaround till I get it fixed might be to create dummy fields that return the interface type.
Since there are no actual fields that return the interfaces, it doesn't know what class to map them to. It should be filtering them out, and I'll fix that as soon as I can.
Activity
apottere commentedon Jul 27, 2017
I think I know what's causing this, and a workaround till I get it fixed might be to create dummy fields that return the interface type.
Since there are no actual fields that return the interfaces, it doesn't know what class to map them to. It should be filtering them out, and I'll fix that as soon as I can.
Add test for multiple interfaces that aren't used as field types (fixes
Implement field datafetchers and multiple root resolvers (fixes #35, f…