Interaction and server state
Keep ephemeral interaction local while applications retain authoritative, durable, and security-sensitive state.
On this page
Datastar interaction
Datastar is the Components interaction model. Sparse local signals hold ephemeral state such as whether a menu is open or which option is active. Selected form values and editable queries are submitted intentionally.
Treat Datastar expressions and endpoints as trusted application code and never interpolate untrusted content into executable expressions.
Server-owned state
Applications continue to own authoritative options, routes, permissions, validation, persistence, actions, and error handling. Remote Combobox results return only the stable options morph region.
Application boundaries
- Keep product routes, authorization, domain formatting, query behavior, and durable state in the application.
- Keep table querying, sorting, filtering, pagination, chart data, and drawing application-owned.
- Use Datastar rather than adding a parallel Alpine or client-side component runtime.