NanamiAdmin
c7642ecca5
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.
39 lines
1.9 KiB
JavaScript
39 lines
1.9 KiB
JavaScript
import http from '../utils/http.js';
|
|
|
|
export const authApi = {
|
|
login: (username, password) => http.post('/user/login', { username, password }),
|
|
register: (username, password) => http.post('/user/register', { username, password })
|
|
};
|
|
|
|
// /api/server/getStatus?uuid=all → { success, message, data: { "<uuid>": { uuid, name, online, report } } }
|
|
export const serverApi = {
|
|
statusAll: () => http.get('/server/getStatus?uuid=all'),
|
|
infoAll: () => http.get('/server/getInfo?uuid=all')
|
|
};
|
|
|
|
// /api/settings/get?type=… / /api/settings/set?type=…
|
|
// get → { success, message, data: { config } }.
|
|
// set → { success, message, data: { type, restartRequired } }, where
|
|
// restartRequired lists the keys the update changed that are only read at
|
|
// startup, so the caller can say which edits are not live yet. It is
|
|
// always an array, empty when the whole update took effect.
|
|
// `type` is one of global | bot_user_config | bot_node_config.
|
|
// For set, pass a partial object; a JSON null value removes that key.
|
|
export const settingsApi = {
|
|
get: (type) => http.get(`/settings/get?type=${encodeURIComponent(type)}`),
|
|
set: (type, patch) => http.post(`/settings/set?type=${encodeURIComponent(type)}`, patch)
|
|
};
|
|
|
|
// Incoming webhook endpoints (admin). They live in the `webhook.endpoints`
|
|
// section of config.json, but are managed here rather than through the settings
|
|
// API because they are a keyed collection: add/modify take one endpoint object
|
|
// and change only the fields they carry, and a new endpoint is rejected with
|
|
// 409 when its name is taken.
|
|
// list → { success, message, data: { endpoints: { "<name>": { enabled, token, notifyPipes } } } }.
|
|
export const webhookApi = {
|
|
list: () => http.get('/webhook/list'),
|
|
add: (endpoint) => http.post('/webhook/add', endpoint),
|
|
modify: (endpoint) => http.post('/webhook/modify', endpoint),
|
|
remove: (name) => http.post('/webhook/delete', { name })
|
|
};
|