Tags: KitBurgess/graphql-kotlin
Tags
[build] update all generated pom.xml with sonatype information (Exped… …iaGroup#736)
[build] attempt to use default mavenJava publication for plugin (Expe… …diaGroup#735) Our current build does not upload Gradle plugin jar artifact to Sonatype. Reverting back to the original publication logic - originally had an issue with mutliple artifacts sharing the coordinates, checking if that is still an issue. If nothing else works we might need to disable Sonatype publish of Gradle artifact for now.
[build] fix publishing of Gradle plugin marker (ExpediaGroup#733) Current logic was incorrectly attaching project sources+javadoc to the Maven publication. Since Gradle plugin produces two publications -> plugin + plugin marker both of them were uploaded with attached plugin sources+javadoc jars.
[plugin] update Maven Mojo names to follow hyphen-name (ExpediaGroup#719 ) * [plugin] update Maven Mojo names to follow hyphen-name Maven plugins generally follow `hyphen-name` for defining different Mojos and build lifecycle phases. Updating GraphQL Kotlin Maven plugin to follow the convention. * fix build We can execute multiple goals in single execution OR specify execution IDs for each execution
[plugin] update generated GraphQL client execute query method (Expedi… …aGroup#711) Update generated client query method from `<operationName>` to simple `execute`, e.g. given operation name `HelloWorldQuery` we would end up generating it as `HelloWorldQuery.helloWorldQuery`, instead we will now generate it as `HelloWorldQuery.execute`.
update release process to publishPlugin after sonatype publish (Exped… …iaGroup#704) Recent RC releases were failing to publish sonatype but were successfully publish Gradle plugin. Attempting to publish plugin only after successful sonatype publish by explicitly specifying tasks to execute. Unfortunately cannot easily configure the order using `build.gradle.kts` as `finalizedBy` clause will always run finalized tasks regardless whether previous one succeeded or not. New release command `./gradlew :initializeSonatypeStagingRepository publish :closeAndReleaseRepository publishPlugins -Pversion=${NEW_VERSION}`
Add extends directive if not defined (ExpediaGroup#702) * Add extends directive if not defined Since the extends directive is always used in federation on the Query object we should always have the directive definition in the schema. However it may already be added if the generated schema uses it, so only add the definition if it is not yet defined * Add all directive definitions even if not used Co-authored-by: Shane Myrick <[email protected]>
Remove GraphQLID annotation for ID class (ExpediaGroup#700) * Add ID wrapper class Add a simple wrapper class that will allow us to support List<ID> Fixes ExpediaGroup#698 * Remove @GraphQLID annotation * Add more unit tests for coverage * Update docs/writing-schemas/scalars.md Co-authored-by: Dariusz Kuc <[email protected]> * Update docs to match example code * Update docs language Co-authored-by: Shane Myrick <[email protected]> Co-authored-by: Dariusz Kuc <[email protected]>
PreviousNext