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
Currently the extension can only be executed if the user has open in VSCode a single devtools folder. In the scenario of the user having vscode open with multiple folders the extension won't work.
Solution:
When the user is in a folder with mutiple folders open all the sfmc devtools extension actions should take in consideration the path from the project in order to switch and execute the action in the selected project.
Possible solution: vscode.workspace.workspaceFolders and execSync("cd && mcdev ....")
just in case users have multiple project folders open, you should always match whatever path you get from a context menu execution to then be able to switch the current working directory to the right root folder!
mcdev expected to be executed in the root folder of a project because that's where it will look for the config file .mcdevrc.json and .mcdev-auth.json
as expected, running any context-menu related commands wont bother checking or changing the working directory but simply take whatever terminal is currently open, paste & execute the relevant command. that ends in the following error:
The text was updated successfully, but these errors were encountered:
Currently the extension can only be executed if the user has open in VSCode a single devtools folder. In the scenario of the user having vscode open with multiple folders the extension won't work.
Solution:
When the user is in a folder with mutiple folders open all the sfmc devtools extension actions should take in consideration the path from the project in order to switch and execute the action in the selected project.
Possible solution: vscode.workspace.workspaceFolders and execSync("cd && mcdev ....")
The text was updated successfully, but these errors were encountered: