new Maven plugin with introspect schema mojo #674
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR introduces new graphql-kotlin Maven plugin with schema introspection functionality (same functionality as provided by Gradle plugin). This new plugin MOJO runs introspection query against target GraphQL endpoint and generates GraphQL schema based on the results. PR size is very large due to inclusion of raw introspection result used for integration testing as well as Maven wrapper scripts - together those files amount to over 2300 lines of code. NOTE: This is a 2nd PR that attempts to split up ExpediaGroup#595 into more manageable pieces. Subsequent PRs will follow with additional functionality.
dariuszkuc
added
changes: minor
Contributor
|
@dariuszkuc Do we need to somehow enable a local m2 repository directory for builds in actions? |
Integration test pom.xml file references project that will be added in subsequent PRs
Collaborator
Author
|
@smyrick we don't have to do anything but it I think we could potentially use .m2 caching there as well. Unfortunately caching action does not support multiple paths atm (scheduled for v2) so we need to run it twice. |
Contributor
|
@dariuszkuc I meant as a way to fix the build. It looks like it was a code issue though. For implementing the action cache I think we can just skip that for now |
smyrick
reviewed
Apr 28, 2020
smyrick
approved these changes
Apr 28, 2020
dariuszkuc
added a commit
to dariuszkuc/graphql-kotlin
that referenced
this pull request
Aug 5, 2022
* new Maven plugin with introspect schema mojo This PR introduces new graphql-kotlin Maven plugin with schema introspection functionality (same functionality as provided by Gradle plugin). This new plugin MOJO runs introspection query against target GraphQL endpoint and generates GraphQL schema based on the results. PR size is very large due to inclusion of raw introspection result used for integration testing as well as Maven wrapper scripts - together those files amount to over 2300 lines of code. NOTE: This is a 2nd PR that attempts to split up ExpediaGroup#595 into more manageable pieces. Subsequent PRs will follow with additional functionality. * fix copy-paste error Integration test pom.xml file references project that will be added in subsequent PRs * configure maven cache for integration tests * missed one more dependency that will be added later on... * update maven cache to account for java version
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📝 Description
This PR introduces new graphql-kotlin Maven plugin with schema introspection functionality (same functionality as provided by Gradle plugin). This new plugin MOJO runs introspection query against target GraphQL endpoint and generates GraphQL schema based on the results.
PR size is very large due to inclusion of raw introspection result used for integration testing as well as Maven wrapper scripts - together those files amount to over 2300 lines of code.
NOTE: This is a 2nd PR that attempts to split up #595 into more manageable pieces. Subsequent PRs will follow with additional functionality.
🔗 Related Issues
None