Issue: Opening the parent folder of a frontmatter project will have frontmatter use it as a project as well

Describe the bug When setting the vscode working folder to the parent of several Front Matter projects, the parent is treated as the default frontmatter project.

To Reproduce Steps to reproduce the behavior:

1. Create three fromtmatter test projects in a folder labeled test
2. Open the folder test in VS Code as the workspace
3. Open a markdown file in one of the front matter projects
4. Select the extension Front Matter

Note that Front Matter asks you to promote “local settings” to “global settings”. Note that a frontmatter.json file is added to the non frontmatter project folder test

Expected behavior Front Matter shouldn’t be greedy and claim folders to be projects that is not meant to be projects. If the root of a workspace doesn’t contain a .frontmatterfolder, it’s not a Front Matter project.

Screenshots

Desktop (please complete the following information):

• Version: 1.74.0 (user setup)
• Commit: 5235c6bb189b60b01b1f49062f4ffa42384f8c91
• Date: 2022-12-05T16:38:16.075Z
• Electron: 19.1.8
• Chromium: 102.0.5005.167
• Node.js: 16.14.2
• V8: 10.2.154.15-electron.0
• OS: Windows_NT x64 10.0.19044
• Sandboxed: No
• FrontMatter: 8.2.0

Additional context Add any other context about the problem here.

[dennisl68-castra]

I’m on Christmas vacation at the moment, but will get back to you next week.

[estruyf]

Thanks and happy holidays @dennisl68-castra