[breaking] Deprecate and drop graphql-java-support-api module
dariuszkuc opened this issue · comments
graphql-java v17 introduced new GraphQLContext mechanism which standardized how context should be utilized. Prior to v17, context could be of any object and it was up to the developers to decide how it should look like. This old "any" object context mechanism is currently deprecated and will be removed in future versions of graphql-java. New GraphQLContext standardizes the approach and is a simple wrapper around a map.
graphql-java-support-api contains single HTTPRequestHeaders interface that was used by old/deprecated context mechanism to indicate whether GraphQLContext ("any" object) supports federated tracing. Since this context mechanism is deprecated in graphql-java, we should also deprecate it in federation-jvm.
Starting with v0.9.0, federation-jvm already supports FederationTracingInstrumentation through the new GraphQLContext map mechanism.
Deprecated in #315