How to use LegacyCoercingInputInterceptor in v22 #3594
-
It seems v21 uses this by default, but I can't figure out how to enable the LegacyCoercingInputInterceptor in v22. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
The code that uses this callback is still in place in V22 - but it being on by default has changed the value conversion code does
So you need to place a It will then run that code during value conversion The reason it was removed in the V22 breaking change version is that we wanted to move to a more spec compliant value conversion and the breaking change version was the time to do it. We knew it may hurt some people relying on old value shapes so we pre built this conversion callback to allow people to go back to the old ways if need be |
Beta Was this translation helpful? Give feedback.
The code that uses this callback is still in place in V22 - but it being on by default has changed
the value conversion code does
So you need to place a
LegacyCoercingInputInterceptor
into the requestsgraphql.GraphQLContext
under the keygraphql.execution.values.InputInterceptor
class.It will then run that code during value conversion
The reason it was removed in the V22 breaking change version is that we wanted to move to a more spec compliant value conversion and the breaking change version was the time to do it. We knew it may hurt some people relying on old value shapes so we pre built this conversion c…