breaking: drop deprecated graphql-java-support-api package #335
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.
This PR drops the
graphql-java-support-api
package.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 ofgraphql-java
. "New" GraphQLContext standardizes the approach and is a simple wrapper around a map.graphql-java-support-api
contained singleHTTPRequestHeaders
interface that was used by old/deprecated context mechanism to indicate whetherGraphQLContext
("any" object) supports federated tracing. Starting with v0.9.0,federation-jvm
already supportsFederationTracingInstrumentation
through the new GraphQLContext map mechanism.Resolves: #190