import { type AstNode } from './util';
/**
 * ESLint rule definition shape used by `require-action-error-handler`.
 */
export interface DbxWebRequireActionErrorHandlerRuleDefinition {
    readonly meta: {
        readonly type: 'suggestion';
        readonly fixable: 'code';
        readonly docs: {
            readonly description: string;
            readonly recommended: boolean;
        };
        readonly messages: {
            readonly missingErrorHandler: string;
        };
        readonly schema: readonly object[];
    };
    create(context: AstNode): Record<string, (node: AstNode) => void>;
}
/**
 * ESLint (Angular template) rule that flags a `dbxAction` which runs work (has a
 * handler or a trigger) but presents no errors to the user.
 *
 * Satisfied by ANY error directive in the context: `dbxActionSnackbarError`,
 * `[dbxActionError]`, `[dbxActionSnackbar]`, or `[dbxActionErrorHandler]`.
 *
 * Shares the same context-scoping bail conditions as `require-action-value-source`
 * (`[dbxActionSource]` on self/ancestor, or a nested `dbxAction`).
 *
 * The autofix appends the bare `dbxActionSnackbarError` token to the action host's
 * start tag — the canonical default, and the form every compliant call site uses.
 *
 * IMPORTANT: `DbxActionSnackbarErrorDirective` is a standalone directive from
 * `@dereekb/dbx-web`, so the fix is only complete once the component also lists it
 * in `imports`. A template fixer cannot add that (for an external `.html` the
 * imports live in a different file entirely), and Angular does NOT reject an
 * unmatched bare attribute — it degrades to an inert DOM attribute. So `--fix`
 * silences this rule whether or not the import lands. Always add the import
 * alongside the fix, and prefer `dbxActionErrorHandler` (which lives in
 * `@dereekb/dbx-core`) wherever a dbx-web dependency would be a layering violation.
 */
export declare const DBX_WEB_REQUIRE_ACTION_ERROR_HANDLER_RULE: DbxWebRequireActionErrorHandlerRuleDefinition;