Skip to content

make ObjectMappers consistent across GraphQLResponse and GraphQLClients #2159

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

regulskimichal
Copy link

@regulskimichal regulskimichal commented May 14, 2025

Pull request checklist

  • Please read our contributor guide
  • Consider creating a discussion on the discussion forum
    first
  • Make sure the PR doesn't introduce backward compatibility issues
  • Make sure to have sufficient test cases

Pull Request type

  • Bugfix
  • Feature
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Other (please describe):

Changes in this PR

Currently there is an issue related to the recent changes that induced GraphQLRequestOptions and refactoring of createCustomObjectMapper() method, that makes it impossible to use custom ObjectMapper during deserialization of data in GraphQLResponse

Alternatives considered

Describe alternative implementation you have considered

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant