Customize ObjectMapper / inject custom ObjectMapper

[benneq]

Currently the default Spring ObjectMapper is injected.

But in many applications it is already widely used and cannot be customized for graphql.

In my case a legacy app uses ObjectMapper with setSerializationInclusion(Include.NON_NULL). This will break lot's of graphql clients. But I can't change it, because a lot of stuff within the legacy app relies on that behavior.

[marceloverdijk]

Similar as graphql-java-kickstart/graphql-java-servlet#42

Maybe something like a GraphQLObjectMapperProvider interface can be introduced which has a GraphQLObjectMapperProvider implementation that simply takes the general ObjectMapper in the application context.

[jsdevel]

yea, there really shouldn't be a hardcoded objectMapper. I'm attempting to implement this in hybris, and am not able to use the Jackson object mapper.

[marceloverdijk]

For Micronaut-GraphQL we introduced a GraphQLJsonSerializer abstraction.
Maybe this could inspire graphql-java-spring as well. See micronaut-projects/micronaut-graphql@9a51982 for details.

[andimarek]

I like the Serializer abstraction mentioned by @marceloverdijk, I think this is the way to go. Anyone interested in creating a PR? @marceloverdijk @jsdevel @benneq ?

[marceloverdijk]

@andimarek I will provide a PR this week.

[andimarek]

@marceloverdijk thanks a lot

[andimarek]

solved via #10

[jsdevel]

@andimarek when will 2.0 be released?