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
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.
@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.
project-labelsbot
added
In BETA
The current task is available for testing in the BETA version.
To document
This item needs to be documented
and removed
In progress
This is actively being worked on
In BETA
The current task is available for testing in the BETA version.
To document
This item needs to be documented
labels
Apr 1, 2024
estruyf
added
Released
The task has been released
and removed
In BETA
The current task is available for testing in the BETA version.
labels
Apr 12, 2024
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 #774 (comment)
The text was updated successfully, but these errors were encountered: