Appearance
apps/panel 0.78.0
Released on 2 September 2026. Previous release: 0.77.0.
What changed
- An HTTP action with a modal editor now reads each field's
typeand renders the corresponding scalar control. ABooleanfield appears as a checkbox; after the user selects it, the panel sends JSONtrueorfalseinstead of a string. - When the user selects Apply, the panel sends the complete editor form as the request body without converting its typed values. This preserves numeric values and JSON objects, including objects that contain a
valueproperty. The submitted form replaces a configuredrequest.body; aPOST,PUT, orPATCHaction without an editor continues to send its configured body unchanged. - Row layouts, hidden and read-only values, lists, comments, regular-expression checks, and defaults remain available in the HTTP editor. Hidden and read-only values remain in the submitted form.
Configuration behavior
Existing configurations that use type: "Boolean" require no migration. The panel applies defaultValue only when the field is absent, so an existing false, null, zero, or empty string is preserved. A Boolean field without row data or a default can remain absent from the request body, and the current editor does not enforce required.
If an endpoint requires a non-null Boolean, set a Boolean defaultValue for a possibly absent field and ensure the source row does not supply null. If the endpoint rejects the request, the panel shows the endpoint error and leaves the modal open. Correct the configuration or source data before selecting Apply again; retrying unchanged input sends the same value.
The HTTP editor does not support editor.tabs or the Object selector. Use a scalar identifier field when the request must contain an object identifier.
Updated documentation
- Configure typed HTTP action fields explains the complete nesting, request-body precedence, supported field metadata, local example, and current limitations.