[Feature] Hidden Plugin Configuration
Opened this issue · 4 comments
The current Plugin configuration system is great. But sometimes you want to store complex data for your plugin.
Here is an example of my current attempt to save QuickEdit's configuration in STRING variables (this is done through the GQL API, the actual configuration is a long JS object that no user would input manually).
This continues for... more than 200 lines of json text.
What I would like is the ability to store this configuration in a Hidden state, to avoid overloading the config screen.
This could be achieved by adding a "Hidden" setting to each configuration in the Plugin yaml file. Or by having a "BLOB" type of configuration which does not display the value and is only used by the plugin directly through the API ?
+1 to this for sure.
I accidentally discovered this and it should technically be a bug but
the configuration field as via GQL is just free text, having it in the .yml means it's displayed to the user. If you change the key name or just write to an empty key, it will be accessible, but not accessible to the user as long as the key name is different
Good to know, means it should not be a big change to the code to make this possible.
But I'd rather not use a bug. I can wait a little longer for the feature to be officially available.
The .yml just makes the field present to the user, not sure what difference code would make, changing it to be strict in the backend might be more trouble than it's worth