alex/manage
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Make service connection config editable on service page

Browse Source 
The service detail page showed non-secret connection config (base_url,
user_id, username, timeout_seconds) as read-only. Render schema-driven
editable inputs (reusing the create-dialog pattern) with a draftConfig
state hydrated from the instance, and unify the save button to persist
both config and secrets. Number fields render as type=number; the base_url
schema description surfaces as helper text.
This commit is contained in:
Developer
2026-06-26 09:52:43 +00:00
parent eebc86a52b
commit 3d331e4c72
19 changed files with 149 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files
backend/src/.pi-map.md
+2 -2
View File
@@ -4,10 +4,10 @@ dir: backend/src
index: backend/src/.pi-map.index.md
## role
Backend application source directory containing the core business logic, API endpoints, data models, and server configuration for the project.
Root source directory serving as the main entry point and organizational container for the backend application.
## files
## arch
Likely follows a layered/n-tier architecture (controllers/services/models) with possible modular or hexagonal patterns; structure depends on framework conventions (e.g., Express, NestJS, Django, Spring Boot).
Standard layered architecture entry point, typically initializing the application, wiring up configurations, modules, routes, and services (e.g., MVC, modular monolith, or Clean Architecture).
## tags
-
## symbols