Skip to content

fix(Combobox): Show all options in single mode when a value is selected #2505

fix(Combobox): Show all options in single mode when a value is selected

fix(Combobox): Show all options in single mode when a value is selected #2505

Triggered via pull request May 14, 2024 10:04
Status Success
Total duration 2m 43s
Artifacts

checks-packages.yml

on: pull_request
Builds, lints and tests code
2m 32s
Builds, lints and tests code
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Builds, lints and tests code: apps/storefront/components/Blog/Contributors/Contributors.tsx#L14
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Builds, lints and tests code: apps/storefront/components/ComponentCard/ComponentCard.tsx#L17
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Builds, lints and tests code: apps/storefront/components/Image/Image.tsx#L17
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Builds, lints and tests code: apps/storefront/components/Section/Section.tsx#L37
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Builds, lints and tests code: apps/storefront/components/Tokens/TokenList/TokenList.tsx#L204
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Builds, lints and tests code: apps/storefront/pages/bloggen/testing.mdx#L20
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element