Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Hidden Plugin Configuration #5511

Open
S3L3CT3DLoves opened this issue Nov 27, 2024 · 4 comments
Open

[Feature] Hidden Plugin Configuration #5511

S3L3CT3DLoves opened this issue Nov 27, 2024 · 4 comments

Comments

@S3L3CT3DLoves
Copy link

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).

image
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 ?

@Valkyr-JS
Copy link

+1 to this for sure.

@feederbox826
Copy link
Contributor

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

@S3L3CT3DLoves
Copy link
Author

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.

@feederbox826
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants