feature to disable auto save when clicking run the code

Is your feature request related to a problem? Please describe.

I wonder if we can add option to disable auto-save when run the code or not provide it as default. It can be a checkbox above Run The Code button that disable saving.

Describe the solution you’d like

would it be good to add save button that run function, instead of automating save when Run the code is clicked.

for people who don’t need or use it, because for example we use Text-editor, and testing people code from the forum we can disable it.

but the people who need it should know about, so they don’t lose their code because they didn’t click Run the Code before closing the tab, we can disable auto save when clicking Run the Code and add a shiny button that saves instead.

Describe alternatives you’ve considered

and I hope to make it will be something resembles codepen save button later, but with different options like a toggle Save on click Run the code, or disable save for a day, preview your code in a modal, open console in modal,

Additional context

I am not saying disable auto save entirely, I just think people who don’t need or use it can disable it. and people who need it but leave the editor before clicking Run The Code have an option to save their code.

[moT01]

Just test in an incognito window or browser where you are signed out.

[moT01]

No, we do not have auto-save

Quite sure it works like this: -save button -> saves to savedChallenges -run tests -> saves to local storage - there may be some improvements around that we can make - specifically, when we should clear it -submit challenge -> saves to savedChallenges and completedChallenges + clears local storage

-loading code -> looks in savedChallenges for code first, then local storage

for people who don’t need or use it, because for example we use Text-editor, and testing people code from the forum we can disable it.

So what’s happening for you @Sboonny, is you test someones code -> click run -> it saves to local storage. You must not have anything saved for that challenge in the database, so it loads the local storage. I believe this (local storage behavior) is the same as any of the other challenges, you maybe just don’t really notice cause you’re tending to an influx of issues around the new cert projects - and most other challenges are a few lines of code. The JS cert projects would be the other place you would notice it pretty good.