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
Stash treats plugin settings as undefined until the user manually changes them, however their default appears as 0 numbers and false for booleans. This is problematic for users updating these values in the first instance, when a default should have a higher number or true as the default. For example, Most Appears With should show a default of 3, not 0.
This can potentially be set with a subscription to check when the plugin is installed or updated, and when triggered run a mutation on the plugin settings. This may not work, however.
The text was updated successfully, but these errors were encountered:
This seems possible on updating packages, but not on installing packages, which is the ideal time for it to run. The GQL seems to need to run within a PluginApi.patch.... So this can't run immediately on install.
Even if this was possible, it would be a pretty hacky way to do it. The ideal way would be to have a native defaultSettings property in the plugin yaml file, like defaultArgs for tasks. Will raise as a request and revisit this issue if/when that is implemented.
Stash treats plugin settings as undefined until the user manually changes them, however their default appears as
0
numbers andfalse
for booleans. This is problematic for users updating these values in the first instance, when a default should have a higher number ortrue
as the default. For example, Most Appears With should show a default of 3, not 0.This can potentially be set with a subscription to check when the plugin is installed or updated, and when triggered run a mutation on the plugin settings. This may not work, however.
The text was updated successfully, but these errors were encountered: