What gets changed in the API file when switching query to custom?
As you can see in the video below, when switching a query in the query builder to custom it dirties the file without actually changing anything.
It then asks to save the file before closing. What has changed when switching to custom?
dirtyfile
Well changing the query type is already a change, no matter if you go back.
But what gets changed in the code? Isn’t this then dangerous to switch views?
The code between simple query and custom query is very different even if the end result might be the same.
So then it is a very bad idea to do it unless you have no other choice.
I was hoping that switching views would allow me to see the results of the query (which it does). But I see that is now a bad idea. There should be a warning or something? 
Use Git and see every single thing that might have changed.
For experimenting with “running” a query, I would recommend to just duplicate the step, convert to custom, run it, then delete the step.
I get an error after update to 5.2
If you have any issues, please create a separate topic with detailed explanation what is wrong.
You need to enable the experimental features 
Ah! There it is! Love it! Thanks! 
Best new feature since v5 was released.
