_resetYasgui url param does not work anymore to delete browser storage

[JJ-Author]

while http://yasgui.org/?a=b&_resetYasgui deletes your local storage this seems not to work anymore for the new yasgui 4 version

[LaurensRietveld]

Interesting to see that this was used. Could you elaborate a bit more on your use case? Perhaps there is a better solution that is visible to more users than the ones 'in the know'

[JJ-Author]

Sometimes it happened that the local storage got messed up because of one strange tab which got somehow broken. Then this was useful to send the user having trouble this link. Moreover when I improved yasgui settings, this was not reflected without deleting local storage. As a computer scientist myself I can also use the dev tools to delete local storage or disable it permanently during development. But maybe for others an option to reset in the GUI instead would be helpful?

So if it was intended that it does not work anymore you can of course close the issue.

[LaurensRietveld]

Thanks for the explanation.
Would the following suit your use cases?

• a button in the yasgui settings to 'reset yasgui'
• better error handling for irrecoverable errors, such as an error dialog with the option the reset yasgui

Ps. Next time you have such an error, could you submit your local storage value in an issue? I recall having similar issues in the previous version, and want to avoid such fragile behavior in this new release

[JJ-Author]

Thanks for the explanation.
Would the following suit your use cases?

• a button in the yasgui settings to 'reset yasgui'

Yes this sounds great. and I would be happy about it.

• better error handling for irrecoverable errors, such as an error dialog with the option the reset

I don't know what you mean by irrecoverable errors, but yes this also sounds good. But it would not be a 'must-have' for us at the moment.

Ps. Next time you have such an error, could you submit your local storage value in an issue? I recall having similar issues in the previous version, and want to avoid such fragile behavior in this new release

Alright I will. So far I did not have trouble like this in the v4.