import { KVL } from "../../ldaccess/KVL";
import { LDOwnProps, LDRouteProps, LDConnectedState, LDLocalState } from "../../appstate/LDProps";
import { IReactCompInfoItm } from "../reactUtils/iReactCompInfo";
import { BlueprintConfig } from "../../ldaccess/ldBlueprint";
export declare function generateIntrprtrForProp(kvStores: KVL[], prop: string, retriever: string, routes: LDRouteProps): any;
export declare function generateCompInfoItm(kvStores: KVL[], prop: string, retriever: string): IReactCompInfoItm;
export declare function generateAllCompInfoItms(kvStores: KVL[], prop: string, retriever: string): IReactCompInfoItm[];
/**
 * use this function in a react component for sub-render functions that return a component
 * example usage:	private renderSub = generateItptFromCompInfo.bind(this);
 * render(){<>{this.renderSub(VisualDict.inputContainer)}<>}
 * @param compKey the key of the itpt-kv, e.g. VisualDict.inputContainer
 */
export declare function generateItptFromCompInfo(compKey: string, routes?: LDRouteProps, index?: number): JSX.Element;
/**
 * initializes the state of a BlueprintInterpreter along with react interpreters
 * @param cfg the BlueprintConfig to initialize from, usually: this.cfg = (this.constructor["cfg"] as BlueprintConfig);
 * @param props props of a component that are relevant for the ld-part
 * @param itptKeys //
 * @param kvKeys //
 * @param itptIsMulti //
 * @param kvIsMulti //
 * Optimization note: For performance reaosons, initialization of the state's react-part and
 * ld-part are combined. Check commit 59b2a48 and previous to compare
 */
export declare function initLDLocalState(cfg: BlueprintConfig, props: LDConnectedState & LDOwnProps, itptKeys: string[], kvKeys: string[], itptIsMulti?: boolean[], kvIsMulti?: boolean[]): LDLocalState;
export declare function gdsfpLD(props: LDConnectedState & LDOwnProps, prevState: null | LDLocalState, itptKeys: string[], kvKeys: string[], canInterpretType?: string, itptIsMulti?: boolean[], kvIsMulti?: boolean[]): LDLocalState | null;
/**
 * used e.g. for BaseDataTypeInput. When generic containers deconstruct the object given to them, they
 * construct interpreters based on the type of that object's properties. To display that property name
 * as a description in the interpreter, we need to determine its key. For example:
 * {myTimesheetContainerData: {workhours: 7.7, date: 2018-06-09, forProject: 'Customer Project 1'}}
 * would result in a container splitting myTimeSheetContainerData up into three interpreters,
 * workhours with a number double input field and "workhours" as the description,
 * date with a date input and "date" description, and a text field containing "Customer Project 1"
 * and "forProject" as the description
 * @param kvStores the kvStores to determine singleKVKey from
 */
export declare function determineSingleKVKey(kvStores: KVL[], canInterpretType: string, inKeys: string[]): string;