feat: improve top-level Query and Mutation type handling

[danadajian]

📝 Description

• Includes a generated class per field for the top-level Query and Mutation types.
• Includes the Query and Mutation types in resolverInterfaces by default.

🔗 Related Issues

• Support breaking up Query class into individual classes for Inheritance #71

[MicahWitthaus]

I see there is an expected.kt for the new query field classes but I didn't see any tests using it in this PR. Are the tests generated somewhere in this repo?

[danadajian]

I see there is an expected.kt for the new query field classes but I didn't see any tests using it in this PR. Are the tests generated somewhere in this repo?

So each directory in the unit/ folder contains an expected.kt and schema.graphql file. The schema.graphql file should generate the expected.kt

[MicahWitthaus]

So each directory in the unit/ folder contains an expected.kt and schema.graphql file. The schema.graphql file should generate the expected.kt

@danadajian Gotcha, so there are no assertions checking that the schema.graphql file actually generates the expected.kt contents?

[danadajian]

So each directory in the unit/ folder contains an expected.kt and schema.graphql file. The schema.graphql file should generate the expected.kt

@danadajian Gotcha, so there are no assertions checking that the schema.graphql file actually generates the expected.kt contents?

There are, they are just done in a slightly abstract way in plugin.test.ts

[github-actions]

🎉 This PR is included in version 3.2.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 3.3.0-alpha.1 🎉

The release is available on:

• GitHub release
• npm package (@alpha dist-tag)

Your semantic-release bot 📦🚀