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
When I'm just getting started, I personally find it useful to write out the schema and then run graphiql against it to test out queries. Unfortunately I need to write data classes for the entire schema in order to even start the application, which makes this very tedious. Being able to configure it to not care about this would be helpful so that it can be built a piece at a time.
Closing as not planned. Fields without a resolver build now with allowUnimplementedResolvers or missingResolverDataFetcherProvider, and a type with no class can be mapped to a Map with dictionary("Hero", HashMap::class.java) + includeUnusedTypes(true). If you just want to try queries in GraphiQL before writing any code, graphql-java's UnExecutableSchemaGenerator.makeUnExecutableSchema(...) builds a schema straight from the SDL.
Activity
apottere commentedon Jul 11, 2017
I like this idea - would it just throw exceptions if you tried to request a field that didn't have an associated object?
sazzer commentedon Jul 11, 2017
Allow modification of generic 'wrapper' types (fixes #47) and begin s…
oryan-block commentedon Oct 18, 2026
Closing as not planned. Fields without a resolver build now with
allowUnimplementedResolversormissingResolverDataFetcherProvider, and a type with no class can be mapped to aMapwithdictionary("Hero", HashMap::class.java)+includeUnusedTypes(true). If you just want to try queries in GraphiQL before writing any code, graphql-java'sUnExecutableSchemaGenerator.makeUnExecutableSchema(...)builds a schema straight from the SDL.