Vscode-extension-for-zowe: Refreshing job list more than once doesn't collapse tree node

Created on 27 Aug 2019  路  6Comments  路  Source: zowe/vscode-extension-for-zowe

Steps to reproduce:

  1. Add a profile to the Jobs tree that contains several jobs and expand it.
  2. Click the Refresh button next to the profile name. The job list collapses and must be expanded again, which I believe is expected behavior.
  3. With the job list expanded, click the Refresh button again. Now the list disappears, but the arrow next to the profile node is still expanded. Now I need to click twice, once to collapse the node and again to expand it. If this step is repeated, the same strange behavior occurs.
bug

Most helpful comment

Thanks @Colin-Stone. I think the key oddity here, was that once you hit refresh, you had to close the folder, then open it again to see the list.

I think the former version refreshed the list in place, so no additional user action was required to see the jobs.

All 6 comments

  1. Click the Refresh button next to the profile name. The job list collapses and must be expanded again, which I believe is expected behavior.

After discussing with @tucker01, not sure if this is expected behavior. Should the job list be able to stay expanded when it refreshes?

The rule I applied across the three views was if you collapse and then expand a node e.g. the root, the content stays as it was as in every child that was expanded remains expanded. No server calls made. Alternatively if you perform a refresh I treat is as a clean slate and remove all child elements from the node being refreshed. This avoids multiple calls to the server to reinstate the same situation as before.

The Jobs view is slightly different to the other views (having an additional refresh button) I do intend to align it with the other two views

Thanks @Colin-Stone. I think the key oddity here, was that once you hit refresh, you had to close the folder, then open it again to see the list.

I think the former version refreshed the list in place, so no additional user action was required to see the jobs.

I can't recreate this issue. Maybe some code has addressed this already. Could you try again with the 0.25+ version please?.

I'm also no longer to reproduce this issue, it appears to have been fixed. Thanks :)

"Back of the net...." Thanks Timothy.

Was this page helpful?
0 / 5 - 0 ratings