refactor(Combobox): ♻️ Move styling to combobox.css
#2491
Barsneschecks-packages.yml
on: pull_request
Builds, lints and tests code
2m 35s
Annotations
2 errors and 6 warnings
|
packages/react/src/components/form/Combobox/Combobox.test.tsx > Combobox > should remove all values when we click on the clear button:
packages/react/src/components/form/Combobox/Combobox.test.tsx#L201
Error: Could not find clear button
❯ packages/react/src/components/form/Combobox/Combobox.test.tsx:201:13
|
|
Builds, lints and tests code
Process completed with exit code 1.
|
|
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
|