10 Commits

Include renames

Author	SHA1	Message	Date
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	ac5587d0c8	fix(handler): read the data envelope in the server endpoint tests ... TestServerGetInfoAll, TestServerGetInfoSingleAndMissing and TestServerGetStatusAll indexed the decoded response by uuid at the top level, but utils.SendSuccessResponse wraps the payload as {success, message?, data:{...}} — the shape the console reads as response.data[uuid] (frontend/src/api/index.js). The uuid lookups therefore always missed, and unmarshalling the nil raw message surfaced as "unexpected end of JSON input". decodeResponse now decodes the envelope, asserts it is a success carrying a data object, and returns that object. The handlers are unchanged: they already return the documented shape.	2026-09-28 23:03:45 +08:00
NanamiAdmin	3877c6d128	feat(webhook): implement management API for incoming webhook endpoints	2026-09-24 12:32:22 +08:00
NanamiAdmin	057d7d584d	feat: add incoming webhook API support with configurable endpoints ... - Implemented the incoming webhook API to handle alerts from external applications. - Added configuration options for webhook listening address, port, and endpoints in config.go. - Created WebhookReceiverConfig and WebhookEndpointConfig structures to manage webhook settings. - Developed WebhookHandler to process incoming requests, validate tokens, and deliver alerts to specified channels. - Enhanced existing controller interfaces to support alert delivery. - Updated message rendering to respect Markdown settings for different channels. - Added tests for webhook functionality and ensured proper error handling.	2026-09-24 11:21:38 +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	786f364743	feat(user): implement registration for the first user with concurrency handling	2026-09-08 22:53:02 +08:00
NanamiAdmin	a0e2df615c	feat: add /api/server/getInfo to handle frontend get server info. ... chore: rebuild `/api/server/getStatus` to the same logic as `getInfo`.	2026-09-08 22:28:49 +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
NanamiAdmin	1d09765a4a	chore(qq_napcat): rewrite all napcat_bridge logic into this project to replace adapt into napcat_bridge	2026-08-05 17:07:29 +08:00
NanamiAdmin	19b69acc29	feat: finish project basic structure and core functions	2026-08-03 22:15:53 +08:00