Feature request: GM Value persistence APIs

[SilverEzhik]

Greasemonkey and other user script managers include asynchronous APIs which can be used to save and load string/integer/boolean values:

• GM.setValue
• GM.getValue
• GM.deleteValue
• GM.listValues

This allows creating user scripts which can persist values across websites or allow for configuration by the user without modifying the script source. For example, I could add a checkbox to temporarily enable debug output in my script and have that change persist across page reloads and domain changes.

I think this is the only feature I'm missing, absolutely loving using this on iOS otherwise :). Being able to point the userscripts folder to cloud storage and having everything automatically update as I edit scripts from my PC is a godsend.

[quoid]

Thanks for the request @SilverEzhik - adding additional GM api methods are next on the list (after getting these current versions released).

[quoid]

@SilverEzhik newest iOS and macOS builds will have these methods exposed to the user

[SilverEzhik]

Awesome, I can confirm that it works with my scripts, though it looks like @grant only checks for GM_ and not GM.

Also, taking a quick look at the source, it looks like GM_ and GM. variants are identical, but there's actually a difference between the two since GM_ variants are synchronous while GM. variants are supposed to be asynchronous. This is fine for me since I've already been using asynchronous variants, but if backwards compatibility is a concern, it might be better to remove GM_ variants and leave a note in the documentation pointing to async variants.

Here's a relevant discussion for a different user script manager with a similar issue: erosman/support#98

[SilverEzhik]

By the way, Violentmonkey has a good reference for all the GM APIs: https://violentmonkey.github.io/api/gm

[quoid]

@SilverEzhik

Also, taking a quick look at the source, it looks like GM_ and GM. variants are identical, but there's actually a difference between the two since GM_ variants are synchronous while GM. variants are supposed to be asynchronous. This is fine for me since I've already been using asynchronous variants, but if backwards compatibility is a concern, it might be better to remove GM_ variants and leave a note in the documentation pointing to async variants.

Thank you very much for this info. I had no idea of these differences. I think considering this, I will remove the GM_ variants and update @grant to check for GM.. If backwards compatability is desired, the old GM_ variants can always be added in at a later date.

Thanks again

[quoid]

merged b8b8a7f