import { type Argv } from 'yargs';
import { type FormatAndWriteItemConfig } from './format.js';
import { type InputProcessorFlags } from './input-builder.js';
import { type InputProcessor } from './input-processor.js';
import { type ActionFunction } from './io-defs.js';
import { type BuildOutputFormatterFlags } from './output-builder.js';
import { type SmartThingsCommand, type SmartThingsCommandFlags } from './smartthings-command.js';
export type InputAndOutputItemFlags = InputProcessorFlags & BuildOutputFormatterFlags & {
    dryRun?: boolean;
};
export type InputAndOutputItemConfig<O extends object> = FormatAndWriteItemConfig<O>;
export declare const inputAndOutputItemBuilder: <T extends SmartThingsCommandFlags>(yargs: Argv<T>) => Argv<T & InputAndOutputItemFlags>;
/**
 * This is the main function used in most create and update commands. It parses input and passes it
 * on to the executeAction function parameter.
 *
 * By default input is only accepted from stdin or a file specified by the --input command line
 * flag as JSON or YAML but alternate input processors can be specified as arguments. They need to
 * implement the InputProcessor<I> interface. The most common use-case for this is to use a Q&A
 * session with the user to build up the input. Another possible use-case would be building input
 * from command line flags or arguments. Input processors are called in the order they are specified
 * and the first one to return data is used.
 */
export declare const inputAndOutputItem: <I extends object, O extends object = I>(command: SmartThingsCommand<InputAndOutputItemFlags>, config: InputAndOutputItemConfig<O>, executeAction: ActionFunction<void, I, O>, ...alternateInputProcessors: InputProcessor<I>[]) => Promise<void>;
//# sourceMappingURL=input-and-output-item.d.ts.map