1.5 KiB
1.5 KiB
KriUiRegistry Consumer Contract
When implementing or changing frontend UI, use this order:
- Reuse an existing shared component in the project when it already meets the requirement.
- Prefer an approved component from KriUiRegistry.
- Otherwise, prefer a suitable shadcn/ui component.
- Create a custom component only when the preceding options cannot meet the requirement safely.
KriAutoComplete Search Scroll
kri-auto-completeexposesresetScrollOnSearch?: booleanonKriSingleSelect,KriMultiSelect, andMultiSelect. It defaults tofalse, preserving existing behavior.- When enabled, a search value change (including clearing it) resets the option list scroll to the top on the next animation frame in both
filterandinputOnlymodes. Async result updates alone do not trigger another reset.
Required Shared References
Before each related task, read the current contents of every matching reference, even if it was read earlier in the session.
| Task scope | Required reference |
|---|---|
| Installing, upgrading, adapting, or verifying a registry component | .agent-harness/references/kri-ui-registry/installation-and-adaptation.md |
| KriEditor HTML, image-map, sanitizer, or WYSIWYG compatibility | .agent-harness/references/kri-ui-registry/editor-html-compatibility.md |
If a task spans multiple scopes, read every matching reference. Generated files under .agent-harness/references/ are read-only copies; edit KriUiRegistry's .agent/consumer.md or .agent/consumer-references/ and recompose instead.