Documents saga a2ui 1.0.0 (stable). This catalog entry is generated from the package manifests and entry points at source revision 15591e3. It is published as a snapshot: later source changes do not alter it. Licensed under Apache-2.0.
A control whose layout names no action. The application attaches an action to each rendered instance, so one definition serves every row while each row keeps its own state.
Renderers: Lit and React.
Entry points
Exports
The names below are read from the entry point sources at the pinned revision.@saga-a2ui/core/actions/action-button-schema
Source: entry point at the pinned revision.
Values: ActionButtonApi.
Types: none.
@saga-a2ui/react/actions
Source: entry point at the pinned revision.
Values: ActionButton, ActionButtonEntry, ActionsScope, InstanceHostProvider, createReactActions, useActionSetup.
Types: ActionButtonActivation, ActionButtonEvents, ReactActions, ReactActionsOptions.
@saga-a2ui/lit/actions
Source: entry point at the pinned revision.
Values: ActionButton, ActionButtonElement, actionButtonEntry, createLitActions.
Types: ActionButtonActivation, ActionButtonEvents, LitActionsOptions.
Static demonstration
Two ActionButton instances in a row of the notes application’s layout. Neither names an action. It is a copy of lines fromexamples/pack1-consumer/src/notes-surface.ts at the pinned revision, not a live rendering.
Usage
- Change a component and trace allowed and denied requests
- Component definition, template and instance
Qualification
- The notes application runs with Lit controls and, through a React consumer, with React controls. (Renderer evidence)
- In Claude and ChatGPT, in-card server requests are allowed or refused for the signed-in account.