Add local schema file support to Gradle plugin extension (ExpediaGrou…

…p#1212)

* Add local schema file support to Gradle plugin

* update new property to schemaFileName

* fix test - use absolute path for schema file

Co-authored-by: Scott Rossillo <[email protected]>

[plugin] better error messages when generating clients (ExpediaGroup#…

…1182)

* [plugin] better error messages when generating clients

Adds operation name to all thrown exceptions so it is easier to find the invalid file.

Resolves: ExpediaGroup#1173

* separate invalid polymorphic selection set exceptions

* fix unit tests

Client Generation - Allow schema to be on the classpath (ExpediaGroup…

…#1136)

* Client Generation - Allow schema SDL to be on the classpath

* Suggestions and Refactors

* Minor touchup

* More improvements to the code, remove redundant edits

Add valid locations annotation (ExpediaGroup#1132)

* Add valid locations annotation

* Update annotation input

* Mark function as interna;

[plugin] fix compile dependency of test client (ExpediaGroup#1124)

`GraphQLGenerateTestClientTask` was extending `GraphQLGenerateClientTask` which meant that we were configuring all task of type `GraphQLGenerateClientTask` we were also configuring test client. Moved the common client generation logic to a new `AbstractGenerateClientTask` which is used by both client generation tasks.

[docs] fix subscription docs and formatting (ExpediaGroup#1121)

[docs] fix subscription docs and formatting (ExpediaGroup#1121)

Call hooks for return type on properties (ExpediaGroup#1112)

Co-authored-by: Shane Myrick <[email protected]>

[build] update release build to automatically release to nexus (Exped…

…iaGroup#1093)

This is a follow up to ExpediaGroup#1091 which seems to be working fine.

[client] generate enums in UPPERCASE and fix kotlinx request serializ…

…ation (ExpediaGroup#1087)

Update client generation logic to always generate enums in UPPERCASE and then use corresponding Jackson (`@JsonProperty`) or kotlinx-serialization (`@SerialName`) annotation to convert those back to expected schema values. This allows us to support enum values that cannot be used directly in Kotlin (i.e. `name` and `ordinal`) as they would clash with built in methods.

This PR also resolves incorrect serialization of requests when using `kotlinx-serialization`. We were applying our custom `AnySerializer` to serialize the requests which was in turn incorrectly serializing enums and custom scalars. I changed the logic to construct correct `KSerializer` based on the specified request.

Resolves: ExpediaGroup#1075