isolatedDeclarations does not support well-known symbols as properties

[MichaelMitchell-at]

Tested version: 0.16.3

> require('oxc-transform').isolatedDeclaration('hello.ts', `
    export class Foo {
      [Symbol.hasInstance](): boolean {
        return false;
      }
    }
`)
{
  sourceText: 'export declare class Foo {}\n',
  errors: [
    'TS9038: Computed property names on class or object literals cannot be inferred with --isolatedDeclarations.'
  ]
}

Expected:

export declare class Foo {
    [Symbol.hasInstance](): boolean;
}

Actual:

export declare class Foo {}

TS behavior for reference

[Dunqing]

https://www.typescriptlang.org/play/?noCheck=true&isolatedDeclarations=true&isolatedModules=true#code/KYDwDg9gTgLgBAYwDYEMDOa4DEITgbwCg44BtAZQE8BbAIwiQDoALdASQDs0YUOFgAugAoAlAC449BsF4FiJOFGAwArlA5wAZiiRpgAbnkBfQkaA

TypeScript reports the same error

[MichaelMitchell-at]

This was fixed in a more recent version of TypeScript, specifically in this PR: microsoft/TypeScript#58771

If you switch the version used in the playground to nightly, the error no longer exists.

[Dunqing]

This was fixed in a more recent version of TypeScript, specifically in this PR: microsoft/TypeScript#58771

If you switch the version used in the playground to nightly, the error no longer exists.

Thank you for your mentioning this. We will support this soon

[Dunqing]

It may be released in TypeScript 5.6, So it's not a high priority at the moment for us. If anyone is interested, feel free to send a PR!

[MichaelMitchell-at]

Looks like SWC recently added support for this: swc-project/swc#9869

Looks like they're using some of the test cases I wrote in: #4099

Their code change is surprisingly small though. I guess their AST processing model makes this more straightforward for them.

[MichaelMitchell-at]

microsoft/TypeScript#60052 was recently merged though. When TS starts allowing any computed property of the form "a.b.c" under isolated declarations, it will make this issue a specific sub-case of an easier-to-implement one.