You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's possible during development (or now) to get Script Lab in a state where it can't load. With OfficeDev/script-lab#722, even uninstalling, restarting, and reinstalling doesn't clear out the old cache, so there's no easy-to-moderate way to get Script Lab back to a useable state.
One possible suggestion is that if the code pane doesn't load within 30 seconds, an option to clear the cache and reset to the production build is presented.
The text was updated successfully, but these errors were encountered:
FYI, you can "hard reset" yourself by attaching a debugger to the add-in and then doing "window.localStorage.clear()" in the console and then reloading the add-in.
This is a critical feature. There are multiple instances of Script Lab customers getting trapped due to the current state. I've had it happen to me several times.
Currently the way to do this is to:
open F12 tools
clear out local storage
However, customers don't know the inner workings of Script Lab.
We can do this by adding a new button on the menu that opens a separate tools html page with the option to reset to factory state. We can allow them to download all of their snippets before they do this, and also give them the possibility to upload their snippets.
Description:
It's possible during development (or now) to get Script Lab in a state where it can't load. With OfficeDev/script-lab#722, even uninstalling, restarting, and reinstalling doesn't clear out the old cache, so there's no easy-to-moderate way to get Script Lab back to a useable state.
One possible suggestion is that if the code pane doesn't load within 30 seconds, an option to clear the cache and reset to the production build is presented.
The text was updated successfully, but these errors were encountered: