feat(FilterListBox): add component

[tenphi]

No description provided.

[changeset-bot]

🦋 Changeset detected

Latest commit: 97d074b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@cube-dev/ui-kit	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
cube-ui-kit	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 18, 2025 11:06am
cube-ui-kit-cursor	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 18, 2025 11:06am

[github-actions]

📦 NPM canary release

Deployed canary version 0.0.0-canary-804cf9f.

[github-actions]

🏋️ Size limit report

Name	Size	Passed?
All	264.44 KB (+0.83% 🔺)	No 👎
Tree shaking (just a Button)	21.74 KB (+0.05% 🔺)	Yes 🎉
Tree shaking (just an Icon)	11.41 KB (0% 🟰)	Yes 🎉

---

Click here if you want to find out what is changed in this build

[github-actions]

🧪 Storybook is successfully deployed!

• 👀 Review changes: https://www.chromatic.com/build?appId=626ee6db91d1c8004a912249&number=1875
• 👨‍🎨 Preview storybook: https://626ee6db91d1c8004a912249-erehdsvajo.chromatic.com/

[cursor]

Bug: Search Comparison Uses Incorrect Property

The doesTermExist function in FilterListBox.tsx incorrectly compares the search term against an item's key instead of its displayed text content (textValue or children). This leads to duplicate custom options being shown when the search term matches an existing item's display text but not its key, as the function fails to identify the existing option. The comparison should be against the item's display text, ideally case-insensitively.

src/components/fields/FilterListBox/FilterListBox.tsx#L341-L351

cube-ui-kit/src/components/fields/FilterListBox/FilterListBox.tsx

Lines 341 to 351 in 97d074b

	if (child.type === Item) {
	const childText =
	child.props.textValue ||
	(typeof child.props.children === 'string'
	? child.props.children
	: '') ||
	String(child.props.children ?? '');
	if (term === String(child.key)) {
	exists = true;
	}

Fix in Cursor • Fix in Web

---

Bug: FieldWrapper Fails to Apply Styles Without Labels

The FieldWrapper component now bypasses its rendering and returns the wrapped component directly when no label prop is provided. This prevents components from receiving essential field-level functionalities, such as validation states, error messages, required indicators, descriptions, and other styling or accessibility features, which are needed regardless of label presence.

src/components/form/wrapper.tsx#L40-L43

cube-ui-kit/src/components/form/wrapper.tsx

Lines 40 to 43 in 97d074b

	if (!label) {
	return component;
	}

Fix in Cursor • Fix in Web

---

Was this report helpful? Give feedback by reacting with 👍 or 👎