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
What is the current behavior?
I want to be able to create a project for a customer. Inside a directory I want to create multiple SPGo instances for different site collections, e.g.:
<Customer>/packages/<site_collection>/src
<Customer>/packages/<site_collection>/SPGo.json
and
<Customer>/packages/<site_collection 2>/src
<Customer>/packages/<site_collection 2>/SPGo.json
In this example, SPGo will fail when run in the root dir <Customer>. It will only work, when VSCode was opened in the correct root folder, e.g. <Customer>/packages/<site_collection>.
What is the expected behavior?
When running any SPGo command that uses the file's context, i.e. Publish a major version of the current file, the extension should pick the closest SPGo.json file it can find.
The text was updated successfully, but these errors were encountered:
I'm submitting a ...
What is the current behavior?
I want to be able to create a project for a customer. Inside a directory I want to create multiple SPGo instances for different site collections, e.g.:
<Customer>/packages/<site_collection>/src
<Customer>/packages/<site_collection>/SPGo.json
and
<Customer>/packages/<site_collection 2>/src
<Customer>/packages/<site_collection 2>/SPGo.json
In this example, SPGo will fail when run in the root dir
<Customer>
. It will only work, when VSCode was opened in the correct root folder, e.g.<Customer>/packages/<site_collection>
.When running any SPGo command that uses the file's context, i.e.
Publish a major version of the current file
, the extension should pick the closestSPGo.json
file it can find.The text was updated successfully, but these errors were encountered: