fusion/.changeset/fix-notification-settings-persistence.md at 4f23883bac0ff8b1f5a2441a164b73d82d1cd422

Files

gsxdsm 192ea195f7 feat(FN-1627): expose global execution concurrency limit in settings

- Add global max concurrent agent limit to settings UI (Scheduling section)
- Add null-as-delete semantics for global settings persistence
- Add fetchGlobalConcurrency and updateGlobalConcurrency API integrations
- Update SettingsModal tests with comprehensive coverage for new features
- Fix lint issues in modified files

2026-04-13 20:22:10 -07:00

638 B

Raw Blame History

@gsxdsm/fusion

@gsxdsm/fusion
patch

Fix notification settings persistence when clearing fields

Previously, clearing notification fields (ntfyTopic, ntfyDashboardHost, ntfyEvents) in the Settings modal would not persist - the old values would remain. This was because undefined values are dropped during JSON serialization.

Now uses null-as-delete semantics: when a user explicitly clears a notification field, the dashboard sends null to the server, which explicitly removes the field from settings and falls back to defaults on next read.

Fixes the round-trip: Save + reopen settings now correctly shows cleared notification fields.

638 B Raw Blame History

638 B

Raw Blame History