[
https://issues.apache.org/jira/browse/SLING-12818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Schulze updated SLING-12818:
-----------------------------------
Description:
With the update of the graphql-java library form 20.9 to 24.0, variables
(Float, Int, Boolean) have to be handed over in the correct casted type, not as
a string anymore. To have the same behaviour we have to introduce
LegacyCoercingInputInterceptor [1]
[1]
https://github.com/graphql-java/graphql-java-page/blob/master/documentation/upgrade-notes.md#how-to-use-the-inputinterceptor-to-use-the-legacy-parsevalue-behaviour-prior-to-v220
was:
With the update of the graphql-java library form 20.9 to 24.0, variables
(Float, Int, Boolean) have to be handed over in the correct type. To have the
same behaviour we have to introduce LegacyCoercingInputInterceptor [1]
[1]
https://github.com/graphql-java/graphql-java-page/blob/master/documentation/upgrade-notes.md#how-to-use-the-inputinterceptor-to-use-the-legacy-parsevalue-behaviour-prior-to-v220
> GraphQL variables has to be casted to the correct type
> ------------------------------------------------------
>
> Key: SLING-12818
> URL: https://issues.apache.org/jira/browse/SLING-12818
> Project: Sling
> Issue Type: Bug
> Components: GraphQL
> Affects Versions: GraphQL Core 0.0.32
> Reporter: Martin Schulze
> Priority: Major
>
> With the update of the graphql-java library form 20.9 to 24.0, variables
> (Float, Int, Boolean) have to be handed over in the correct casted type, not
> as a string anymore. To have the same behaviour we have to introduce
> LegacyCoercingInputInterceptor [1]
> [1]
> https://github.com/graphql-java/graphql-java-page/blob/master/documentation/upgrade-notes.md#how-to-use-the-inputinterceptor-to-use-the-legacy-parsevalue-behaviour-prior-to-v220
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
