- Issue created by @ricovandevin
- @ricovandevin opened merge request.
- Status changed to Needs review
over 1 year ago 11:21am 16 August 2023 - 🇮🇹Italy reinchek Napoli 🌋, 🇮🇹
Hi @ricovandevin, thanks for your contribution!
Can you attach an example case just to better understand the issue?Anyway, reviewing the MR's code i guess that, clarified the mechanism, i will merge as soon as possible.
-
reinchek →
committed a7a53b6a on 2.0 authored by
ricovandevin →
Issue #3381426 by ricovandevin: String arguments should not be JSON...
-
reinchek →
committed a7a53b6a on 2.0 authored by
ricovandevin →
- 🇮🇹Italy reinchek Napoli 🌋, 🇮🇹
Hi @ricovandevin, i've tried the use case (argument as string and not object/array) and your code works good.
I'm merging right now the MR.Thanks.
- Status changed to Fixed
over 1 year ago 6:50pm 16 August 2023 - Status changed to Fixed
over 1 year ago 6:48am 17 August 2023 - 🇮🇹Italy reinchek Napoli 🌋, 🇮🇹
Message in a bottle:
I've created a new release 2.0.5 → that includes:- #3381426 - String arguments should not be JSON encoded
- #3369542 📌 Automated Drupal 10 compatibility fixes Fixed - Automated Drupal 10 compatibility fixes
- 🇳🇱Netherlands ricovandevin
@reinchek Thanks for picking this up so quickly! An example, just for future reference:
Something like
query: listings: arguments: locale: nl_BE
was sent in the query as
query { search { listings(locale: "nl_BE")
where the API was expecting
query { search { listings(locale: nl_BE)