Files
archie/internal/webui/api_config_repos.go
T
sam 5552ee9c56 feat(webui): inline editing for per-repo allow_concurrent/max_retries/review_enabled
Adds PATCH /api/config/repos/{owner}/{name}, a dedicated seam distinct
from the generic dotted-key PATCH /api/config path: a repository is
one element of []config.Repo, not a flat key. Traced the mechanism
before adding any new plumbing -- overlay.Nest/ApplyOverlayValues
already handle "repos" as a single whole-slice key with no dot, so
the fix is a webui handler plus a bootstrap seam that reads the
daemon's live, untrimmed Repos (never webui.RepoView, which omits
Preflight/TestGlob), mutates the one matched field via the pure
applyRepoFieldUpdate helper, and republishes through the existing
UpdateConfig(ctx, {"repos": repos}) path unchanged.

config-row.js's row() gains an opts.save override so an edit can be
redirected to a different persistence call. The repositories table
renders an autosaving checkbox for the two booleans and a
save-on-blur/Enter input for max_retries, via api.configRepoUpdate.

Closes archie-core-b6ew.6, and with it archie-core-b6ew.
2026-09-02 22:35:03 +10:00

63 lines
2.4 KiB
Go

package webui
import (
"encoding/json"
"errors"
"net/http"
)
// RepoEditableFields are the per-repository fields the dashboard may change
// through handleConfigRepoUpdate. Deliberately narrow: these three are
// booleans/small ints with no cross-field validation, unlike Gate or
// Protect, which stay file-edited (archie-core-b6ew.4/.6).
var RepoEditableFields = map[string]bool{
"allow_concurrent": true,
"max_retries": true,
"review_enabled": true,
}
// handleConfigRepoUpdate applies one field change to one repository,
// identified by owner/name in the path. It exists because the repository
// list is a []config.Repo, not a flat dotted key -- PATCH /api/config's
// generic path (overlay.Nest + configuration.ApplyOverlayValues) has no way
// to address "element N of this slice." UpdateRepoField's implementation
// (wired by the composition root) reads the daemon's own live config.Repo
// values (never the trimmed, wire-safe RepoView), changes just the one
// field, and republishes the full repository list through the same
// validate-persist-publish path PATCH /api/config already uses -- see
// bootstrap.go's installUpdateConfigHandler for why that matters: the wire
// view omits fields (Preflight, TestGlob) that a naive round-trip through
// ConfigView would silently drop.
func (s *Server) handleConfigRepoUpdate(w http.ResponseWriter, r *http.Request) {
if s.UpdateRepoField == nil {
http.Error(w, ErrConfigUpdateUnavailable.Error(), http.StatusServiceUnavailable)
return
}
owner := r.PathValue("owner")
name := r.PathValue("name")
var body struct {
Field string `json:"field"`
Value any `json:"value"`
}
if err := json.NewDecoder(r.Body).Decode(&body); err != nil {
http.Error(w, "invalid request body: "+err.Error(), http.StatusBadRequest)
return
}
if !RepoEditableFields[body.Field] {
http.Error(w, "field "+body.Field+" is not editable from the dashboard", http.StatusBadRequest)
return
}
if err := s.UpdateRepoField(r.Context(), owner, name, body.Field, body.Value); err != nil {
switch {
case errors.Is(err, ErrConfigUpdateUnavailable):
http.Error(w, err.Error(), http.StatusServiceUnavailable)
case errors.Is(err, ErrConfigUpdateInvalid):
http.Error(w, err.Error(), http.StatusBadRequest)
default:
http.Error(w, "repo update failed: "+err.Error(), http.StatusInternalServerError)
}
return
}
writeJSON(w, map[string]any{"ok": true})
}