Export to GitHub causes page refresh and lost changes if you don't store in browser

[annezazu]

Something seems to have changed with Playground and exporting to GitHub. Yesterday, I lost an entire custom setup when exporting because it seems to have reloaded the page when I hit export to github. Here's a quick video replicating:

refresh.mov

To explain, I started a new playground instance, imported a pattern, changed, a style variation, then clicked on "export to GitHub". In the background, it refreshes the instance causing all changes to be lost. To get around this, I needed to store changes in the browser.

[adamziel]

@annezazu the modal warns against that specific scenario and asks to export Playground before proceeding – did you mean the modal wasn't there and the page just reloaded without warning? Or did you mean the modal doesn't communicate the reload problem clearly enough?

[annezazu]

Oh wow. Before, I don't remember this happening when I exported to GitHub so assumed something changed. Maybe I'm just not remembering correctly. I'll close this out in that case :)