The following files get added each time I open a VSCode project and I have to keep deleting them every time I re-open a VSCode project.
Expected behavior
Should only initialize an FM project when the dashboard is first opened.
Probably should ask to do so.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Win 10
**Describe the bug**
**To Reproduce**
Steps to reproduce the behavior:
1. Install Front Matter (non-beta)
2. Open any VS Code project without FM files
3. The following files get added each time I open a VSCode project and I have to keep deleting them every time I re-open a VSCode project.

**Expected behavior**
Should only initialize an FM project when the dashboard is first opened.
Probably should ask to do so.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- Win 10
<!-- github-sync-id:2187883258 -->
That is weird, those files only get generated when the initialize command is executed.
What gets logged to the output in VSCode for Front Matter? https://frontmatter.codes/docs/troubleshooting#looking-what-is-happening-behind-the-scenes
<!-- github-comment-id:1999085944 -->
Can you verify if you have any frontMatter. settings in your ./.vscode/settings.json file? Besides the initialization, there is also an option to create the frontmatter.json file. As the extension verifies, you use any CMS settings in the current project/workspace.
Oh, I might have an idea!
Can you verify if you have any `frontMatter.` settings in your `./.vscode/settings.json` file? Besides the initialization, there is also an option to create the `frontmatter.json` file. As the extension verifies, you use any CMS settings in the current project/workspace.
<!-- github-comment-id:1999096277 -->
settings.json contained this setting but I don't believe I'd ever pressed the "Initialize Project" button.
Oh well at least removing this might cure it.
{"frontMatter.content.pageFolders":[]}
`settings.json` contained this setting but I don't believe I'd ever pressed the "Initialize Project" button.
Oh well at least removing this might cure it.
```json
{
"frontMatter.content.pageFolders": []
}
```
<!-- github-comment-id:2000773035 -->
It could be by accident; the initialize button creates a frontmatter.json file, and settings are added. Only manually can you add settings to the settings.json file.
Good to know it was due to that.
It could be by accident; the initialize button creates a `frontmatter.json` file, and settings are added. Only manually can you add settings to the `settings.json` file.
Good to know it was due to that.
<!-- github-comment-id:2002433883 -->
Ok I'm seeing this issue again in a different workspace with multiple subprojects. I definitely didn't bump the Initialize button on this project. It's creating a frontmatter.json file. Nothing related in ./.vscode/settings.json for either workspace or workspace projects.
I just found that keying Ctrl-S to save a file I've just edited pops up this from FrontMatter asking me to select a workspace project instead of saving the file. So that might explain what's happening.
Ok I'm seeing this issue again in a different workspace with multiple subprojects. I definitely didn't bump the Initialize button on this project. It's creating a `frontmatter.json` file. Nothing related in `./.vscode/settings.json` for either workspace or workspace projects.
I just found that keying `Ctrl-S` to save a file I've just edited pops up this from FrontMatter asking me to select a workspace project instead of saving the file. So that might explain what's happening.

<!-- github-comment-id:2027922254 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Describe the bug
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should only initialize an FM project when the dashboard is first opened.
Probably should ask to do so.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
That is weird, those files only get generated when the initialize command is executed.
What gets logged to the output in VSCode for Front Matter? https://frontmatter.codes/docs/troubleshooting#looking-what-is-happening-behind-the-scenes
Oh, I might have an idea!
Can you verify if you have any
frontMatter.settings in your./.vscode/settings.jsonfile? Besides the initialization, there is also an option to create thefrontmatter.jsonfile. As the extension verifies, you use any CMS settings in the current project/workspace.settings.jsoncontained this setting but I don't believe I'd ever pressed the "Initialize Project" button.Oh well at least removing this might cure it.
It could be by accident; the initialize button creates a
frontmatter.jsonfile, and settings are added. Only manually can you add settings to thesettings.jsonfile.Good to know it was due to that.
Ok I'm seeing this issue again in a different workspace with multiple subprojects. I definitely didn't bump the Initialize button on this project. It's creating a
frontmatter.jsonfile. Nothing related in./.vscode/settings.jsonfor either workspace or workspace projects.I just found that keying
Ctrl-Sto save a file I've just edited pops up this from FrontMatter asking me to select a workspace project instead of saving the file. So that might explain what's happening.@tohagan that is a different kind of issue, will open a new one for it.