It simply impossible to work with lightning components now.

Hi Ilan,

Thank you for sharing this with us.

May I please to clarify some additional details so that we could detect a reason for the issue?

Here are my questions:

1. Please open the Pending Changes panel before deploying your changes and please let me know which files do you have in the list.
2. Please select the necessary file(s) (your helper/controller) there (in the Pending changes list) and deploy them directly from this panel - for this please use the command from the toolbar in this panel.
3. Also, can you please share what do you have in the Output panel as a result of the deployment process.

Looking forward to your response and we would be happy to solve the issue as soon as possible.

Thank you,

Kate

Hi Kate,
I had the same issue when I tried to deploy a modification in a helper.js from a lightning component using "Deploy project (F5)" command. I successfully deploy the code modifying the component too.
Also trying a second time, following the same steps, everything works as expected. I will test more and back here with a set of steps to reproduce this.
Thank you!

I had a similar experience where it deleted everything but the cmp from my bundle.

Kate, I checked the Pending changes and it had nothing under the Working Set or Other metadata.

Once re-created the files and put back all the code, TWS only updated one of the files. I had to quit TWS and re-open to get all the files updated.

At this point, I'm very wary of continuing to use this new version. Is there a way my colleagues who have not yet installed it can opt out of the upgrade until things are settled?

Thanks,

Chris

I think it might be related to the merge functionality when a remote file has been changed since you pulled it and you're trying to update it.

Or possibly to updates where Apex and Lightning resources are both included.

Hi all, 

Thank you for sharing this with us.

We have fixed this problem. You can update your IDE to the last version.

Thank you, Ihor.

Hi guys,

Thank you for prompt sharing this issue - as Ihor wrote, we fixed this.

A reason for the issue was related to the merged mechanism for the deployment functionality for different metadata types - TWS uses different approaches in updating process for different metadata types and some of the cases were not included to this mechanism.

Please let me know if the issue would be reproduced after updating the IDE.

In another case, I'll close the current topic as fixed.

Thank you,

Kate