Open stengvac opened 2 months ago
Or maybe it could be considered feature.
I think this was already reported in #355, although I suppose you consider it a different problem since it's reporting usage at the top level. It worked before we switched to using the ConversionService? I'd have to look into why that is the case, it likely just worked by chance.
Yep I am aware, that top level does not work so we went for input object, which worked.
Will value classes be supported or do we have to swap to non value class? I just want to know what to expect and make adjustments in our code base. Thx.
Hello,
lets say we have value class
we use DGS codegen to generate input and outputs for our server side and we used few value classes for Scalars. In version
8.2.0
it was possible to use scalar in generated input type as one of its fields. Top level value class did not work.Expected behavior
Allow to register converters for
conversionService
inDefaultInputObjectMapper
. It is possible to register custom input object mapper, but as value class is nested in input type, it is not possible to simply register converter only for some types, it require to implement wholeDefaultInputObjectMapper
or I did miss some configuration.I have tried with DGS 8.5.5
Actual behavior
With registered
Coercing<ValueClass, String>
Code like this worked:
This changed with higher versions of DGS as
DefaultInputObjectMapper
got reworked. Now registered coercing is still called, but converter for value class is not found inDefaultInputObjectMapper
.Stack
Steps to reproduce
Create value class. Use it as field in input type. Call query/mutation with such input.