The Ext JS extension leaves .sencha folders in unrelated directories

[BobR]

I use VS Code to open many different directories ('workspaces'), only some of which are actually Ext JS projects.

I've noticed that this extension always creates a .sencha folder.

I believe this extension should not activate, and especially should not create or modify any files, unless it is in an Ext JS project. Perhaps by detecting the existence of the .sencha folder that sencha cmd creates? Or by offering the user the option to mark a project (e.g. by menu, but please not by prompt)?

[petr.vecera]

Hi

Thank for the report. We are aware of this issue and it will be fixed in the future versions.

Petr

[twaindev]

Any ETA on when this will be solved? I currently don't use the plugin because of this bug. I don't like .sencha folders scattered all over my disks.

[petr.vecera]

Any ETA on when this will be solved? I currently don't use the plugin because of this bug. I don't like .sencha folders scattered all over my disks.

Hi

This should be resolved in the latest release.

Regards
Petr

[Mark.Brocato]

Yes, in 1.0.1, it will only add the .sencha directory if it finds another .sencha directory somewhere in the project. The .sencha directory is where IntelliSense index data is stored, so if you have an Ext JS app without a .sencha directory and you're not seeing intellisense you'll need to enable it manually using the "Enable Ext JS IntelliSense for this Project" command via the command palette.

[twaindev]

OK, thank you. I will check it out.

[twaindev]

The update is not available through VSC. Had to download it from the customer portal.