GraphQL can be quite picky about types. :-) The API we have to consume has arguments that need objects as values. Currently JSON encoding is used to turn an array into a string representation of an object that can be used with \GraphQL\RawObject to create an argument value. At least in our case that is not correct as it casts integer values in the object to strings, freaking the API out. :-p
Example config:
query:
search:
listings:
arguments:
customer:
id: 123456
locale: nl_BE
metadata:
size: 400
publication:
changedDateFrom: '2023-08-12T00:00:00.000Z'
it modelled as
query {
search {
listings(
customer: { id: "27299431" }
locale: nl_BE
metadata: { size: 400 }
publication: { changedDateFrom: "2023-08-12T00:00:00.000Z" }
) {
where the API expects
query {
search {
listings(
customer: { id: 27299431 }
locale: nl_BE
metadata: { size: 400 }
publication: { changedDateFrom: "2023-08-12T00:00:00.000Z" }
) {
The customer ID, which is an int, is send as a string.
TBD
Introduce a helper function for creating the object string, wrapping some smart logic that is more respectful to types.
- Design smarter logic for creating the object string
- Create MR
- Review MR
- Merge MR
N/A
N/A
N/A
Closed: works as designed
2.0
Code
This actually seems to work properly. I was adding the customer ID in PHP (in a plugin deriver). I first thought that explicit typecasting in the code did not work. But apparently I forgot to rebuild the caches after adding typecasting of the customer ID to an integer.
Closing this issue as "works as designed" for now.