graphql-java-tools

graphql-java-tools copied to clipboard

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.

I like this idea - would it just throw exceptions if you tried to request a field that didn't have an associated object?

I've no idea to be honest. That's the most obvious solution, but returning null - if the field supports that - could make sense too.

On Tue, 11 Jul 2017 at 17:45 Andrew Potter [email protected] wrote:

I like this idea - would it just throw exceptions if you tried to request a field that didn't have an associated object?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/graphql-java/graphql-java-tools/issues/39#issuecomment-314504044, or mute the thread https://github.com/notifications/unsubscribe-auth/AAECGE39CFPM5UY7bWj_kxu6qOyVgZz3ks5sM6bAgaJpZM4OTjl5 .