Appearance
panel.request.customRequest
GET custom request with a nonempty url; optional dataPath and idField must be nonempty strings when present. idField defaults to id, as in Table; a row without that identity fails the read. Results use common client pagination of 20 rows.
This is a compact property lookup. Use the contextual guide below for the complete feature model, configuration sequence, interactions, examples, and limitations.
- Context
- operatorTerminal panel
- Accepted value
CustomHttpRequestConfig- Required
- No — When metaTypeName is not supplied.
- Default
- No documented default.
User scenarios
- Present operation context while trying the isolated operator terminal demonstration.
Related parameters
Contextual guide and evidence
- Contextual guide: Open the complete human guide
- Source:
apps/panel/src/features/panels/variants/operator-terminal/utils/requests.ts, symbolreadTerminalObjects - Example coverage: Complete — The configured demonstration uses GET /terminal/operations with dataPath operations. The guide explains stable source identifiers, the default id field and client pagination; custom reads do not enable production commands.
- Demo coverage: Partial — Opening the fixture reads operations through GET /terminal/operations and dataPath operations. It exercises the custom source with default id identifiers; other sources and identifier mappings require configuration changes. Open the runnable demo .