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
Just by entering the FrontMatter Dashboard, a .frontmatter folder is created although I've not yet decided to create a FrontMatter project.
To Reproduce
Steps to reproduce the behavior:
Create an empty folder
Open that folder as workspace in VS Code
Select FrontMatter extension
Open the FrontMatter Dashboard.
Expected behavior
FrontMatter shouldn't be greedy and claim folders until I initialize a FrontMatter project. Screenshots
Desktop (please complete the following information):
Version: 1.74.2 (user setup)
Commit: e8a3071ea4344d9d48ef8a4df2c097372b0c5161
Date: 2022-12-20T10:29:14.590Z
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.
The text was updated successfully, but these errors were encountered:
Thanks @DennisL68 for opening this issue, I found the cause and it has been fixed. Now the folder gets created when the project actually get initialized, not before. It is testable in the latest beta version of the extension.
Describe the bug
Just by entering the FrontMatter Dashboard, a
.frontmatter
folder is created although I've not yet decided to create a FrontMatter project.To Reproduce
Steps to reproduce the behavior:
Expected behavior

FrontMatter shouldn't be greedy and claim folders until I initialize a FrontMatter project.
Screenshots
Desktop (please complete the following information):
Version: 1.74.2 (user setup)
Commit: e8a3071ea4344d9d48ef8a4df2c097372b0c5161
Date: 2022-12-20T10:29:14.590Z
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.
The text was updated successfully, but these errors were encountered: