Type casting doesn't work

[FelixLgr]

Hello, I have seen this problem (#109 & #81).
In my case, it does not work. Does anyone have any idea why?

const hasActiveType = filters.some((filter) => (<string[]>Object.values(InvoicesType)).includes(filter.value))

It return :

  "code": "BABEL_PARSER_SYNTAX_ERROR",
  "reasonCode": "UnexpectedToken",

The problem come from <string[]>.

My config :

  "importOrder": ["^src/(.*)$", "^[./]"],
  "importOrderSeparation": true,
  "importOrderSortSpecifiers": true,
  "importOrderGroupNamespaceSpecifiers": true,
  "importOrderParserPlugins": ["classProperties", "decorators-legacy", "typescript", "jsx"]

[steve-taylor]

Babel doesn't support angle-bracket type casting, so you might as well do this instead:

const hasActiveType = filters.some((filter) => (Object.values(InvoicesType) as string[]).includes(filter.value))

If you need any more reasons to use as to cast:

TypeScript 1.6 introduces a new .tsx file extension. This extension does two things: it enables JSX inside of TypeScript files, and it makes the new as operator the default way to cast (removing any ambiguity between JSX expressions and the TypeScript prefix cast operator). For example:

var x = <any>foo;
// is equivalent to:
var x = foo as any;

See https://www.typescriptlang.org/docs/handbook/release-notes/typescript-1-6.html

You might also have luck with

const hasActiveType = filters.some((filter) => (Object.values<string>(InvoicesType)).includes(filter.value))

[maou-shonen]

In one of the projects I manage, I also encountered this issue and came across this discussion.
I mostly agree with the point made by @steve-taylor.
Therefore, I added consistent-type-assertions to the ESLint rules,
hoping it can help save some time for others who encounter this issue in the future :)

// .eslintrc
{
  rules: {
    '@typescript-eslint/consistent-type-assertions': [
      'error',
      {
        assertionStyle: 'as',
      },
    ],
  }
}