Accenture / Accenture/sfmc-devtools-vscode

[BUG] Extension is activated when folder is not a devtools project but there is a mcdevrc file

Open
#240 0 comments 0 reactions 1 assignee View on GitHub

@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:

  1. Create and enter with VSCODE in a empty folder
  2. Create a subfolder and add a .mcdevrc.json file
  3. Reopen VSCode in this previous folder
  4. 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

Image

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.