Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose access to the SchemaParser dictionary #720

Open
3 tasks done
givemetheinternet opened this issue Nov 14, 2022 · 0 comments
Open
3 tasks done

Expose access to the SchemaParser dictionary #720

givemetheinternet opened this issue Nov 14, 2022 · 0 comments

Comments

@givemetheinternet
Copy link

I want to suggest an idea and checked that ...

  • ... to my best knowledge, my idea wouldn't break something for other users
  • ... the documentation does not mention anything about my idea
  • ... there are no open or closed issues that are related to my idea

Description

The mapping from graphql schema type to Java implementation type/class is held in a private member variable dictionary within the SchemaParser class. It would be useful to have the information about this mapping easily accessible (though directly immutable) to clients of the API either through the SchemaParser itself, or the GraphQLSchema that gets finally generated.

Use Cases

This change would enable easier unit/integration testing of applications relying on graphql-java-tools to generate schemas from files. For example, a specific test I need to write must verify that the enum options listed in the schema exactly match the enum options available in the related Java type.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant