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.

_Originally posted by @tohagan in https://github.com/estruyf/vscode-front-matter/issues/774#issuecomment-2027922254_
<!-- github-sync-id:2216353762 -->
@tohagan In the new beta (building atm), a fix prevents FM CMS from starting up when there is no .frontmatter or frontmatter.json file in your workspace. Only when you trigger one of the FM commands will it start. This should prevent it from showing the above workspace folder selection when it doesn't need to do it.
@tohagan In the new beta (building atm), a fix prevents FM CMS from starting up when there is no `.frontmatter` or `frontmatter.json` file in your workspace. Only when you trigger one of the FM commands will it start. This should prevent it from showing the above workspace folder selection when it doesn't need to do it.
<!-- github-comment-id:2027992223 -->
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.
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.Originally posted by @tohagan in https://github.com/estruyf/vscode-front-matter/issues/774#issuecomment-2027922254
@tohagan In the new beta (building atm), a fix prevents FM CMS from starting up when there is no
.frontmatterorfrontmatter.jsonfile in your workspace. Only when you trigger one of the FM commands will it start. This should prevent it from showing the above workspace folder selection when it doesn't need to do it.Thanks very much. Will try to get some time to test the Beta this weekend.