wings-widgets

Built-in widgets

WINGS ships custom elements for common UI so you don't hand-roll them. Each is blank-imported to register, then used as a tag in your template. They emit component events routed to your parent handlers with @event="handler" — the same mechanism in wings-component (handler is a func(args ...any) set in Render; remember the TriggerHandler(nil) placeholder in InitData).

Note on names: @event attribute values (handler names) may be camelCase — attribute values are not lowercased. But any bound attribute name you pass a widget (e.g. nav_input) must be snake_case (gotcha #1).

Button — w-button

import _ "github.com/luisfurquim/wings/widget/button"

<w-button variant="primary" @click="onSave">Save</w-button>
<w-button variant="danger" size="sm" shape="pill">Delete</w-button>
<w-button loading="true">Saving…</w-button>

<!-- icon slots -->
<w-button variant="primary">
  <svg slot="prefix">…</svg>
  Submit
</w-button>

Attributes:

• variant — secondary (default) | primary | ghost | danger | success
• size — sm | md (default) | lg
• shape — default | pill | square
• type — native-like form behavior: inside a <form>, a click submits it (requestSubmit, so constraint validation runs first — invalid w-inputs block it) or, with type="reset", resets it; type="button" opts out. Irrelevant outside a form.
• loading — "true" shows a spinner; button is non-interactive while loading (and never submits)
• disabled — standard HTML; reflected to inner <button> for a11y + keyboard

Boolean attributes take the value "true" (not bare presence) because the WINGS observed-attribute system uses coerceToType against the InitData default: loading="true" sets the bool to true; bare loading sets it to false. Exception: disabled is a standard HTML boolean and IS handled by bare presence.

Clicks bubble naturally through open shadow DOM — use @click on the host as normal. No Go-side Render logic needed for clicks.