All queries that sync to VS-code disappeared from the editor. So all SQL and Javascript-queries are still there, but the code has completly disappeared, while rest-queries are still intact. I tried restoring to a previous release but the problem persists.
The app still works for users, but in the editor it is broken.
I am not sure, but it seems the most probable cause.
Hello @lmolin and @Sam_S, I'm sorry this has happened to both you. I was able to find a report of this issue, where we successfully restored the queries for another user. I merged both of your topics there. This way, we have one place to collect feedback and help users affected by it.
hi @Paulo I jus came across this now and my queries, transformers, JS have also disappeared. I'm using self-hosted... Is there a way you can help me retrieve them?
No problem, since my post, I had no alternative apart from going through each component, 1 by 1 and either rewriting or pulling from anything I had backed up.
I uninstalled the retool extension completely fom vscode; since its still in beta stage I understand that there will be bugs but this one is too impactful.... It did the same thing (wiping ALL codes) from 2 other apps I was working on
The UI was fine, just all the queries and JS in event handlers were all wiped.
Also I still get a pop up that says that 'this code has been changed; refresh or keep mine'
I just shared this post with several engineers to get some attention on this. We should definitely provide a warning for users when viewing the VS Code extension.
The ownership of the extension is in the process of being handed off which has led to this unfortunately not being addressed sooner.
I am happy to hear you were able to build things back to continue moving forward!
For all future users who are thinking of using the Retool extension in VS Code, this is a known issue and we would highly recommend proceeding with caution.
The extension is still in the beta version and our engineers are working on fixing this. I will update this post with any news I hear on this bug and when the extension will be fully safe to use in the future!