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
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.
The text was updated successfully, but these errors were encountered:
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:
Expected behavior
Extension should only be activated when it's a devtools project = mcdevrc.json is in the root folder.
Screenshots
Environment:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: