import { WebComponent } from 'solid-ui'; /** * The small delete control that appears on a contact, a membership or a row of * bad data: it asks for confirmation through the design-system dialog and * reports a failure rather than letting it reject silently. * * The host keeps `data-testid="deleteButtonWithCheck"` because the surrounding * panes hide it until its container is hovered, and those rules match on that * attribute. It replaces UI.widgets.deleteButtonWithCheck, whose own inline * popup would have asked a second time. */ export default class DeleteButton extends WebComponent { static styles: import('lit').CSSResult; /** What is being removed, e.g. 'contact'. Names the button and the prompts. */ accessor noun: string; /** Overrides the default confirmation wording. */ accessor message: string | null; /** Set false when the action confirms on its own -- and can refuse. */ accessor confirm: boolean; /** What to run once the user agrees. */ accessor deleteAction: (() => unknown) | null; /** Let a caller holding the element drive it. Runs the action directly * rather than forwarding to the inner button, which may not have rendered * yet when an imperative caller clicks straight after creating this. */ click(): void; connectedCallback(): void; protected render(): import('lit-html').TemplateResult<1>; private onClick; } /** * Create one for a caller that builds its DOM imperatively. * * Mirrors what UI.widgets.deleteButtonWithCheck did, so the panes that still * assemble their toolbars by hand keep working; a caller rendering with Lit * should use the tag instead. */ export declare function renderDeleteButton(dom: Document, container: HTMLElement, noun: string, deleteAction: () => unknown, options?: { confirm?: boolean; message?: string; }): DeleteButton; //# sourceMappingURL=DeleteButton.d.ts.map