Updating a GraphQL query to add a variable silently clears all existing variable values

💬 Queries and Resources
,
1

Repro steps:

  1. Create a GraphQL query with one or more (mandatory) variables specified.
  2. Confirm that the query can run successfully.
  3. Edit the query to add a new variable.
  4. Run the query or reload the editor.

Expected

The query succeeds, and all the existing variable values are kept after reloading at the step 4.

Actual

The query fails (because the mandatory variables are unspecified), and all the existing variable values are cleared after reloading at the step 4.

A repro video showing adding variable clears the value of an existing variable

1 Like
2

Hi @masaru-iritani Thanks for reporting this! I will reach out when our team is able to ship a fix for this bug. I know it is not ideal, but are you able to re-add the variables in order to move forward?

3

Thank you for your response, Tess! Yes, I can re-add and reconfigure variables after removing existing stale ones or reloading the editor.

I hope it gets fixed soon because our team has already broken apps many times due to this problem :pray:

4

@Tess is there any update on this one? I have lost the progress multiple times by now, we are trying to adopt Retool at Fanatics Live team, but this is frustrating, and error-prune.

The bug was reported long-time ago. I would appreciate some help with it.

5

Hi @yordis,

Unfortunately no update. It looks like this feature request was not on our roadmap but I can bring that ticket back to life and add a +1 to it for you.

Does your Fanatics org have a dedicate TAM? And is it Justin G? He could be a good resource for getting some added attention from engineering on this.

For the short term, although it is not ideal, the work around for this seems to be to copy/paste the query into any other type of code editor (js query, etc.) make changes then paste and in and save the query.

6

That is basically what I learned, CMD+C CMD+V instead of modifying anything :sob:

I am unsure to be honest

7

Sorry again, this is a very irritating bug. I just added another +1 to the bug report ticket so hopefully some engineering attention can get on fixing this as soon as they have bandwidth :sweat:

No worries about the TAM, I checked with him and it seems that he is handling the org with Fanatics Betting and Gaming. So he said this is outside of his scope of coverage, I will keep this post updated with any news I hear on the existing bug ticket I attached this to :crossed_fingers: