Dariusz Kuc

Resolved by https://github.com/ExpediaGroup/graphql-kotlin/pull/1488

Ah indeed, closed incorrectly.

@jmfayard I think it's a great idea but its hihgly unlikely to be implemented anytime soon* (I am no longer with Expedia so may be wrong) *unless someone from community...

I believe the ask was for a convenience on how to generically assign complexity value for given fields. You can specify custom `FieldComplexityCalculator` when creating an instance of `MaxQueryComplexityInstrumentation` but...

Hello 👋 This is indeed an issue with Jackson (kotlinx-serialization does not have this issue) that it does not honor the original field names and instead uses getters to derive...

Hello 👋 Indeed, `graphql-java` loads type definitions and their extensions as two separate objects and we are only looking at the type definitions. Extensions (objects, interfaces, unions, etc) are currently...

Apollo file uploads are not part of the GraphQL specification and are not supported "out-of-the-box". As per #518 you will have to configure Jackson object mapper to correctly handle those...

Currently our handling of polymorphic types as well as default enum values relies on Jackson functionality. As mentioned above I believe we can probably re-implement it using `kotlinx.serialization` which would...

@smyrick this issue is still valid. With the latest change it should be much easier to use on android but we don't publish multiplatform artifacts (yet).

@andylamax currently it is not a priority for us and most likely we won't be working on this in the near future. We are always open to contributions!