Lucio Lelii
19f9fcdbe0
@UiOptionalGroup says what a field is - a group of settings that are all optional - rather than how to draw it. The editor will render it as one control that opens a dialog instead of unfolding five empty chips inline; the read-only execution view will keep showing only what was actually set. Two renderings, one declaration. A field annotation, not a type one, and that is forced rather than preferred. Shared definitions are hoisted into sharedDefinitions only when their JSON is identical in every schema containing them, so a label that varies by owner would un-share ModelParameters silently. The web merges a property's x-ui-* keys over the definition it $refs, so the renderer sees the marker on the object node anyway - the constraint costs nothing. The test asserts the marker is on the property, that the $ref survives beside it, that it is absent from the definition, and that ModelParameters is still shared. Making the label vary by owner fails it. Applied to LLMDescriptor.parameters and to both MCP configurations. Nothing reads it yet; the editor comes next. 534 backend tests green. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .mvn/wrapper | ||
| src | ||
| .gitattributes | ||
| .gitignore | ||
| Dockerfile | ||
| mvnw | ||
| mvnw.cmd | ||
| ollama-preloaded-docker | ||
| pom.xml | ||
| run_service.sh | ||