Accenture / Accenture/sfmc-devtools-vscode
[BUG] Extension is activated when folder is not a devtools project but there is a mcdevrc file
Open
@anasilva105 is already working on this.
Since Mar 13, 2025.
bug
NEW
- Dominant language
- TypeScript
- Stars
- 7
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
The extension is being activated when the folder is not a devtools project but it has the mcdevrc file for example in the node_modules folder.
To Reproduce
Steps to reproduce the behavior:
- Create and enter with VSCODE in a empty folder
- Create a subfolder and add a .mcdevrc.json file
- Reopen VSCode in this previous folder
- Check if the mcdev button appears on the status bar and shows the wrong logs
Expected behavior
Extension should only be activated when it's a devtools project = mcdevrc.json is in the root folder.
Screenshots
Environment:
- OS: win11
- VSCode Version:
- mcdev VSCode Extension Version: 2.2.1
Additional context
Add any other context about the problem here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.