display

package
v0.9.30 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Aug 20, 2026 License: MIT Imports: 5 Imported by: 0

Documentation

Index

Constants

View Source
const (
	ComponentName        = "display"
	InPort        string = "in"
)

Variables

This section is empty.

Functions

This section is empty.

Types

type Component

type Component struct {
	module.Base
	// contains filtered or unexported fields
}

func (*Component) GetInfo

func (t *Component) GetInfo() module.ComponentInfo

func (*Component) Handle

func (t *Component) Handle(ctx context.Context, _ module.Handler, port string, msg interface{}) module.Result

func (*Component) Instance

func (t *Component) Instance() module.Component

func (*Component) OnSettings

func (t *Component) OnSettings(_ context.Context, msg any) error

func (*Component) Ports

func (t *Component) Ports() []module.Port

type Control

type Control struct {
	Text string `json:"text" readonly:"true" format:"markdown" title:"" description:""`
}

Control is the dashboard surface: the text, rendered as prose and not offered for editing.

format:"markdown" is what makes the editor render it instead of putting it in a single-line input, where a paragraph of model output is unreadable and pretends to be typeable. readonly says the obvious thing out loud.

type InMessage

type InMessage struct {
	Text string `json:"text" required:"true" title:"Text" description:"What to show. Markdown is rendered."`
}

InMessage is what to show. A single named field, deliberately: a display panel exists to answer one question, and a flow that wants to surface three things should say which three rather than pushing its whole state at a person.

type Settings

type Settings struct {
	Text string `` /* 186-byte string literal not displayed */
}

Settings carries the panel's authored text — what it shows before any message arrives.

This is what makes a written panel part of the flow rather than a fact about one running copy of it. A readme card receives no messages, so without it the text lived only in node state: it never appeared in an export, and anyone installing the solution got a blank card with nothing to ever fill it.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL