Reverting versions should include showing changes to queries that are open

Let's say I'm editing version 2.2 of my app. When I have a query open, and revert back to (say) version 2.1, the code that is displayed to me stays on version 2.2. The displayed code should change to version 2.1.

This caused me a lot of confusion, because the reason I had the query open was to see how it changed in a different version. I ended up figuring out what was going on and worked around the problem by closing the query and re-opening it every time I changed versions. However, this is a very non-intuitive workflow that should be changed.

Hey @emmamack! Thanks for reaching out.

I agree that this isn't the most intuitive behavior and that it would benefit from an update. There is an existing ticket in our system that I'll bump on your behalf. :+1: As soon as I hear any updates, I'll update the thread here!