Tim Bartley

Fix might just be to duplicate the processing for "Identifier" as "PrivateIdentifier" - I have a local build where this resolves the issue for me but I'm not confident that...

This has been given the label `workaround-available` but the workaround seems to be to use V2 of the SDK. This is not really a work around.

Type safety reduces the maintenance burden on consumers of SDKs enormously. It would be great to see an improvement as suggested here.

+1 for me too.

No worries and thanks for approving! Are the check failures anything I need to look at resolving?

I hit the same issue. I had the following in my eslint config: ``` languageOptions: { parser: tsParser, ecmaVersion: 5, sourceType: 'script', parserOptions: { project: './tsconfig.json', }, }, ``` Removing...