Settings & storage

"settings": [
  {
    "key": "pollInterval",
    "type": "number",
    "label": "Poll interval (seconds)",
    "description": "How often to check for updates",
    "default": 60,
    "min": 10,
    "max": 600,
    "step": 10
  },
  {
    "key": "style",
    "type": "enum",
    "label": "Notification style",
    "default": "compact",
    "options": [
      { "value": "compact", "label": "Compact" },
      { "value": "verbose", "label": "Verbose" }
    ]
  }
]

Use petty.settings.get(key). It returns the stored value, or the manifest default if nothing is stored, or null if neither exists.

var interval = petty.settings.get("pollInterval"); // 60 from manifest if unset
var style = petty.settings.get("style");           // "compact" if unset

Use petty.settings.onChange(key, callback) instead of filtering settings:changed manually. The callback receives the new value directly — not the {key, value} envelope.

petty.settings.onChange("pollInterval", function (newSecs) {
  petty.schedule.interval("poll", newSecs * 1000, poll);
});

Your plugin can update its own settings — useful for persisting state that surfaces in the UI. set dispatches a local settings:changed so your onChange handlers fire. Pass null to delete the stored override and revert to the manifest default.

petty.settings.set("lastSyncedAt", Date.now());
petty.settings.set("style", null); // revert to manifest default

Both APIs persist to UserDefaults under your plugin's namespace — they can't collide. The distinction is declarative intent: