Project tree become unavailable after deleting an OpenshiftConnector component

[musienko-maxim]

Workspace template:

metadata:
  name: test-workspace
projects:
  - name: node-js
    source:
      location: 'https://github.com/maxura/nodejs-hello-world.git'
      type: git
      branch: master
components:
  - id: redhat/vscode-openshift-connector/latest
    type: chePlugin
apiVersion: 1.0.0

Env.: minishift with deployed CHE based on Openshift 3.11, Fedora 29
Steps to reproduce:

1. Create a workspace with Openshift plugin and login into current cluster with UI (we can use the ws. template from this the issue)
2. Create component: select a folder -> new component -> Create new Application -> Provide app name -> Workspace Directory -> select node-js project - Add context folder ...->Provide Component name ->select component type(nodejs latest). Push the component.
3. Delete just created component and switch to the Project explorer

Expected result the Project Explorer should present
Actual result There are no any items.

Screencast:

[vinokurig]

Should be fixed in the upstream: redhat-developer/vscode-openshift-tools#1708

[dgolovin]

Extension is using workspace API to remove specific folder form multi-folder workspace. This kind of use case possible only if you create component in empty workspace. I see you have other folders in workspace before creating new component.
If I do the same steps in vscode it works just fine.

@vinokurig could it be workspace component implementation issue on che side?

[dgolovin]

@vinokurig I think I found the issue. This can be replicated only when folder selected for component is a sub-folder of one used as workspace. Can you test and confirm?

[vinokurig]

@dgolovin
I confirm that the use-case you mentioned above reproduces the issue in CHE and in vscode as well, see the screen cast in the upstream issue.

[ericwill]

Closing this as it's not a Che specific issue.