Cannot open unexpected file types in an Aura Bundle

[Henry Zhao]

How to reproduce:

1. create a random aura component (foobar)
2. give it a controller (foobarController.js)
3. create a typescript variant (foobarController.ts)
4. Try to open the typescript file

Expected: Open the TS file on its own
Actual: Opens the aura bundle .cmp file instead of the TS file, and can never open the TS file at all within the editor

‌

Some clients prefer to have a TS file as a source of truth instead of Aura JS files. I know this is a bit of an edge case and totally not the standard behavior, but it’d be nice if IC2 doesn’t just indiscriminately attempt to open all files in the aura bundle as a sibling of the .cmp file. Otherwise, no other file types can ever be opened.

[Scott Wells]

Henry, you're correct that IC doesn't currently expect to find non-deployable source under the Salesforce metadata directories. Nonetheless, if you guys have figured out how to make TypeScript work for Aura development, I don't want to stand in the way of that! I'll fix the issue that's preventing you from opening those files in the IDE.

[Henry Zhao]

Thanks so much as usual Scott, you’re a lifesaver

[Xander Victory]

Henry are you able to share how you got Typescript to work? i.e. is there a tsconfig.json somewhere in your project?

[Scott Wells]

Delivered in 2.0.9.7. Let me know if it doesn't meet your needs or, worse, causes any issues by side-effect.

[Scott Wells]

Similar support for LWC components delivered in 2.1.0.7.