Dgs headers backward compatibility #2104
Merged
+155
−166
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.
Fix for #2101. Prior to Spring GraphQL integration we could set response headers in two ways:
dgs-response-headers
in theextensions
of anExecutionResult
.DgsExecutionResult
which has aheaders
field.This functionality stopped working, because
DgsExecutionResult
(which was responsible for both mechanisms) was no longer referenced in the framework, so the special handling stopped working.While the now recommended mechanism is to implement a
WebGraphQlInterceptor
to set headers as described in the docs, existing code would have to be updated.This PR adds support for the previous mechanisms. The implementation is now based on a
WebGraphQlInterceptor
.