Workspace wrong population - files renamed and moved out of folder

[tockata]

Hello and thank you for the awesome extension!

I have the following issue while using it:
We have this configuration:

{
"sourceDirectory": "src",
"sharePointSiteUrl": "https://domain/subsiteName",
"publishingScope": "None",
"authenticationType": "Digest",
"remoteFolders": [
"/SiteAssets/**/."
]
}

The real "Site Assets" structure on the server is:
SiteAssets/js/subsiteName111.xxx.js
SiteAssets/js/subsiteName222.yyy.js
SiteAssets/js/subsiteName333.zzz.js

File names start with the same name as the subsiteName.

After populating the workspace the js files are shown outside the js folder and are renamed. The populated structure is the following:
SiteAssets/js111.xxx.js
SiteAssets/js222.yyy.js
SiteAssets/js333.zzz.js

If the file names do not contain the subsite name everything is fine.

[sg-chrishasz]

Hello @tockata - Let me replicate this in my local environment and see what I can find. I suspect this is a case where I made an assumption about site and folder names when doing string operations.

I'll report back when I have a more definitive answer.

[sg-chrishasz]

@tockata I can confirm this is a bug. I will resolve this in the next version of SPGo!

[tockata]

@sg-chrishasz thank you!
When we can expect the next version?

[sg-chrishasz]

@tockata - I am working this issue right now with @koltyakov over here koltyakov/sppull#27. Please feel free to add any additional details I may have missed.

[richyreys]

This is the same problem that i have now.

[sg-chrishasz]

All- I've just posted SPGo 1.3.5 to the VSCode Marketplace which will resolve this issue. Please reopen this issue if you are still experiencing issues.