You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, spo folder copy uses the same endpoint that causes problems with the commands mentioned above, for some reason, there are no limitations for the copying of folders. However, I think it's good to keep these 4 commands aligned and let them use the same endpoint so they behave the same. Additionally, with the current endpoint, it is impossible to know the name of the new copied folder when using --nameConflictBehavior rename. With the new endpoint, this is possible.
The text was updated successfully, but these errors were encountered:
This issue is related to:
spo file copy
#6152spo file move
#6153spo folder move
#6154However,
spo folder copy
uses the same endpoint that causes problems with the commands mentioned above, for some reason, there are no limitations for the copying of folders. However, I think it's good to keep these 4 commands aligned and let them use the same endpoint so they behave the same. Additionally, with the current endpoint, it is impossible to know the name of the new copied folder when using--nameConflictBehavior rename
. With the new endpoint, this is possible.The text was updated successfully, but these errors were encountered: