4 Commits

Include renames

Author	SHA1	Message	Date
NanamiAdmin	aa7e7f87e1	feat(node): add GetNodeCount to get node count and remove no need node update log, only log when node count changed	2026-09-29 21:43:46 +08:00
NanamiAdmin	c7642ecca5	feat(settings): report which saved keys need a restart ... Every settings update answered with a bare success, so the console could not tell a change that took effect at once from one written to the file that the running program would keep ignoring until it was restarted — the listener address, the storage paths, the Komari dashboard URL. Classify the patch instead. config.RestartRequiredKeys expands a patch into the dot-separated paths of its leaves and intersects them with the settings main reads before it starts serving, and the settings endpoint returns that list as data.restartRequired. It is a pure function of the patch, so UpdateSettings keeps its signature and nothing else has to change; the write succeeds either way, and the field only says which edits are not live. Matching is by overlap rather than equality, so a patch that names a section — replacing it, or deleting it with a null — reports the startup-only keys inside it, while a sibling subtree like webhook.endpoints is not mistaken for webhook.enabled. The result is never nil, so an update with nothing to report serializes as [] rather than null and a client can iterate it without a guard. The console reads the field in ConfigSection and warns instead of confirming, naming the keys that are pending; Settings.vue's hints for the Komari URL, the listen address and the storage paths now say which of their fields is affected rather than labelling the whole card.	2026-09-28 23:28:47 +08:00
NanamiAdmin	d96b90b5bf	feat: update API response structure to nest payloads under a single "data" key	2026-09-09 16:15:33 +08:00
NanamiAdmin	4eb9abff49	feat: add /api/settings/get, /api/settings/set to modify config in frontend	2026-09-08 22:13:30 +08:00