Spring Boot Object mapper about graphql-spring-boot HOT 6 CLOSED

I think by default you would expect spring's default object mapper but I also understand that you may want to configure it differently.
Could you add some property like
...graphql.use-default-objectmapper = false and then provide a objectmapper with a certain qualifier?

from graphql-spring-boot.

This is tough because there are cases where you'll want your graphql object mapper to behave differently than your spring object mapper. Passing the spring object mapper to graphql-java-servlet automatically would make it impossible to differentiate.

from graphql-spring-boot.

@oliemansm I have some suggestion to solve this issue.

First we would need to move the instantiations of the per field objectmapper in the to a provider/factory
graphql-java-kickstart/graphql-java-tools@master...mxab:wip/unify-objectmapper
I added also a backward compatible Provider that behaves like the original instantiations using the configurerer.

Similar but only for the one objectmapper that is constructed by the servlet
graphql-java-kickstart/graphql-java-servlet@master...mxab:wip/unify-objectmapper

Finally can provide these providers that just passthrough the available objectmapper provided by spring boot for both tools and servlet
master...mxab:wip/unify-objectmapper

from graphql-spring-boot.

@mxab Nice! I've created PRs for them so we can get them merged and released.

from graphql-spring-boot.

@mxab Can you give me write permissions on your branch in spring-boot? I merged in master to fix conflicts. That has to be pushed before it can be merged.

from graphql-spring-boot.

Cool!

from graphql-spring-boot.