Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
anasilva105 opened this issue Mar 13, 2025 · 0 comments
Assignees
Labels
bug Something isn't working NEW not yet analyzed new issues get this label
Milestone

Comments

@anasilva105
Copy link
Collaborator

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.

@anasilva105 anasilva105 added bug Something isn't working NEW not yet analyzed new issues get this label labels Mar 13, 2025
@anasilva105 anasilva105 added this to the 2.3.0 milestone Mar 13, 2025
@anasilva105 anasilva105 self-assigned this Mar 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working NEW not yet analyzed new issues get this label
Projects
None yet
Development

No branches or pull requests

1 participant