Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Renaming a USS directory changes the tree structure #757

Closed
crawr opened this issue Apr 29, 2020 · 7 comments · Fixed by #971
Closed

Renaming a USS directory changes the tree structure #757

crawr opened this issue Apr 29, 2020 · 7 comments · Fixed by #971
Assignees
Labels
bug Something isn't working USS
Milestone

Comments

@crawr
Copy link
Contributor

crawr commented Apr 29, 2020

When I rename a directory with same name as an existing directory, the directory is moved inside the directory with the same name

@crawr crawr added bug Something isn't working USS labels Apr 29, 2020
@zdmullen
Copy link
Contributor

Can we add a prompt along the lines of "There is already a directory with this name. Do you want to place this..."?

It also keeps the old name of the folder (prior to the rename).

@zdmullen zdmullen added this to the Developer milestone May 27, 2020
@zdmullen
Copy link
Contributor

This is connected to issue #483 and the need for some research/design for the behavior in general.

@zFernand0
Copy link
Member

Having a similar problem after renaming a binary file on a recently renamed directory. 😋

@katelynienaber katelynienaber self-assigned this Jul 30, 2020
@katelynienaber
Copy link
Contributor

Having a similar problem after renaming a binary file on a recently renamed directory. 😋

@zFernand0 Do you mean the issue occurs when you rename a binary file to be the same as the directory name? The old directory name, or the new one? Or do you mean if you rename a binary file, which is inside a recently-renamed directory, the file is moved somewhere?

@zFernand0
Copy link
Member

Having a similar problem after renaming a binary file on a recently renamed directory. 😋

Do you mean the issue occurs when you rename a binary file to be the same as the directory name? The old directory name, or the new one? Or do you mean if you rename a binary file, which is inside a recently-renamed directory, the file is moved somewhere?

The file gets moved outside the directory (at the same level as folder). Hope this helps:

Before renaming the folder

| root
| --folderA
| ----file1.bin 

After renaming the folder

| root
| --folderB
| ----file1.bin 

After renaming the binary file

| root
| --file2.bin
| --folderB

@katelynienaber
Copy link
Contributor

Having a similar problem after renaming a binary file on a recently renamed directory. 😋

Do you mean the issue occurs when you rename a binary file to be the same as the directory name? The old directory name, or the new one? Or do you mean if you rename a binary file, which is inside a recently-renamed directory, the file is moved somewhere?

The file gets moved outside the directory (at the same level as folder). Hope this helps:

Before renaming the folder

| root
| --folderA
| ----file1.bin 

After renaming the folder

| root
| --folderB
| ----file1.bin 

After renaming the binary file

| root
| --file2.bin
| --folderB

I am having trouble reproducing this...I tried renaming the parent directory (folderA) and then renaming the file in the directory (file1.bin) but it left the binary file inside the folder.

Also tried it with a text file but no luck...

@zFernand0
Copy link
Member

I could not reproduce the same issue, even though I ran into a few errors.
I will try to record my Zowe Explorer usage from now own so that I have more steps to replicate any problems I run into.
Thank you for taking the time to try it out! 😋

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working USS
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants