Defaults

provideKikitaUi({
  defaults: {
    size: 'sm',
    button: { shape: 'ghost', size: 'md' },
    select: { clearable: true, maxVisibleChips: 2 },
    toast: { position: 'top-end', duration: 4000 },
  },
});

KuiComponentDefaults lists every key. Interfaces that share a meaning share a base (KuiButtonBaseOptions, KuiFieldControlOptions). Each component page lists its own options in the Provider defaults section.

• Order: local input, then the nearest level, then parent levels, then provideKikitaUi defaults, then the component default.
• An omitted or undefined property inherits from the parent; false, 0, '' and null are real values and override.
• Arrays and functions are replaced as a whole, and a level never changes its parent.
• Several provideKuiDefaults or provideKikitaUi providers on one level combine in provider order, the later one winning per property.

@Service()
class ThemeState {
  readonly shape = signal<KuiButtonShape>('solid');
}

provideKikitaUi({
  defaults: () => ({ button: { shape: inject(ThemeState).shape } }),
});

• Components read the effective value in a computed, so changing the signal updates every affected component. A component providers array cannot read this; put the state in a service and read it in a function.
• set and update write to the nearest level only, and KuiDefaults never exposes a writable signal.
• Dialog, drawer and toast options are read each time one opens, so an open overlay keeps what it opened with, and a tooltip reads its options each time it shows. Toast position and maxVisible belong to the shared region and follow a change of the default. Everything else follows runtime changes immediately.
• Defaults live in the injector of each application instance, so concurrent server requests never share them. Do not keep a module-level signal in an application config shared by requests; create it inside a function default or a service.

• Order: local input, then defaults.<component>.size, then defaults.size, then md. A primitive whose size type is narrower than KuiSize ignores unsupported values; kui-calendar supports sm and md, so a global xs leaves it at md. kui-icon is excluded because its size is a raw CSS size.
• Field controls (kuiInput, kuiTextarea, kuiNumberInput, kuiColorInput, kuiCheckbox, kuiRadio, kuiSwitch) have their own key, and an explicit size on the parent kui-field wins over the control key: local size, then the parent field local size, then defaults.<control>.size, then defaults.field.size, then defaults.size, then md.
• kuiSlider does not read the parent field. kui-field resolves local size, defaults.field.size, defaults.size, md. kuiSelect, kuiCombobox, kuiDatePicker and kuiTimePicker have no size input and follow the parent field.
• kuiButton and kuiIconButton use separate keys because their default shapes differ on purpose (solid for buttons, ghost for icon-only buttons): local input, then defaults.button or defaults.iconButton, then defaults.size.

• Clearable: local input, then defaults.<select|combobox|datePicker|timePicker>, then defaults.field, then the component default. Select defaults to false; Combobox, Date Picker and Time Picker default to true.
• defaults.select.multipleDisplay (chips or text) sets how a multiple select shows its selection and defaults.select.maxVisibleChips how many chips it shows before the +N chip.
• Tooltip: local triggerType, then defaults.tooltip.triggerType, then auto. auto shows on mouse hover and keyboard focus and toggles on touch tap, hover disables touch taps, click uses click or keyboard activation everywhere and none disables the directive. Tooltip content stays supplemental; use a popover for links or buttons.

• Each option resolves as local input or call config, then defaults.<overlay>, then the built-in default.
• kui-dropdown is also the panel of kuiSelect, kuiCombobox, kuiDatePicker and kuiTimePicker, so defaults.dropdown reaches those panels unless the control sets the input itself. kuiDialog and kuiDrawer read the defaults of the injector they are called from, so a nested provideKuiDefaults applies to dialogs opened inside it.

A date picker renders a calendar inside its panel, so a defaults.calendar entry reaches it unless the panel sets the input itself.

Not configurable on purpose: values, open and loading state, disabled, readonly, validation state, data inputs (series, data, groups), ids, accessible names and library message text, and per-instance structure such as Select.multiple, Chip.removable or the OTP length.

provideKikitaUi({ defaults: { icons: { close: MY_CLOSE }, select: { chevronIcon: MY_CHEVRON } } });

Order: defaults.<component>.<slot>Icon, then defaults.icons.<role>, then the built-in glyph. A glyph is plain icon data and an invalid one is ignored. The roles and the data format are listed on the Structural icons page; these are not the icons you pass to kui-icon by name.

A nested level now merges with its parent per property (before, a nested field provider replaced the whole parent object), and kuiDatePicker and kuiTimePicker read their own datePicker and timePicker keys before the field key.