couincouin007 Posts - Answer Overflow

couincouin007

Explore posts from servers

•Created by couincouin007 on 12/8/2023 in #questions

Conflict between shadcn/ui components and @typescript-eslint/no-empty-interface

I have linting errors while using shadcn/ui components because there are some empty interfaces defined extending other supertype interfaces, as : interface CommandDialogProps extends DialogProps {} The @typescript-eslint/no-empty-interface rule prevent the build saying it's an error. I've found that I can configure my eslint rules to satisfy it with:

"@typescript-eslint/no-empty-interface": [
  "error",
  {
    allowSingleExtends: true,
  },
],

"@typescript-eslint/no-empty-interface": [
  "error",
  {
    allowSingleExtends: true,
  },
],

Did you solve this error with another solution? Even if I understand the value of this rule, I think I'm not alone to use shadcn/ui and with the ESLint T3 stack config, this error is boring... On the same subject, the @typescript-eslint/consistent-type-imports rule displays warnings also with shadcn/ui components...

6 replies

Gaming

Programming