Skip to content

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

@anasilva105

Description

@anasilva105

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.

Metadata

Metadata

Assignees

Labels

NEWnot yet analyzed new issues get this labelbugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions