customize
El dominio customize tiene 2 acciones. En la superficie meta se alcanzan todas a través de arcane_customize; en la individual, cada una es una herramienta propia; en la dinámica se ejecutan con arcane_execute_action y el ID canónico.
Resumen
Sección titulada «Resumen»| Acción | Título | Tipo |
|---|---|---|
customize.categories | Get customization categories | lectura |
customize.search | Search customization options | lectura |
Acciones
Sección titulada «Acciones»customize.categories
Sección titulada «customize.categories»Get customization categories
Get all available customization categories with metadata
- Tipo: lectura
- Parámetros obligatorios: ninguno
- Meta-herramienta:
arcane_customizecon"action": "categories" - Herramienta individual:
arcane_customize_categories - Ruta de Arcane:
GET /api/customize/categories - ID de operación:
get-customize-categories - Uso: Static navigation metadata of the web UI’s Customize section: categories templates, registries, variables and git-repositories (only those the caller’s permissions allow), each with id, title, description, icon, url and a settings list of descriptive option entries (key, label, type, description, keywords). Category keywords are always empty. It holds no stored values and nothing reads or writes these options. Manage the real items with template.list, registry.list, variable.list and git_repository.list.
- Acciones relacionadas:
customize.search,template.list,registry.list,variable.list,git_repository.list
customize.search
Sección titulada «customize.search»Search customization options
Search customization categories and options by query
- Tipo: lectura
- Parámetros obligatorios:
query - Meta-herramienta:
arcane_customizecon"action": "search" - Herramienta individual:
arcane_customize_search - Ruta de Arcane:
POST /api/customize/search - ID de operación:
search-customize - Uso: Finds which Customize category covers a word: query (required, non-empty or 400) is matched case-insensitively as a substring against category titles and descriptions and against each option’s key, label, description and keywords, and categories the caller’s permissions hide are dropped. Results are sorted by relevanceScore, and matchingSettings is present only when an option itself matched (e.g. query git returns git-repositories). Use settings.search instead for instance settings.
- Acciones relacionadas:
customize.categories,settings.search,template.list,git_repository.list