New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue: Content folder does not exists, remove it from the configuration does not work with folder setup #788
Comments
Update: it DOES actually add an empty pagefolder variable to From: {
"$schema": "https://frontmatter.codes/frontmatter.schema.json",
"frontMatter.config.dynamicFilePath": "[[workspace]]/frontmatter.config.js",
"frontMatter.site.baseURL": "https://kollitsch.dev"
} To: {
"$schema": "https://frontmatter.codes/frontmatter.schema.json",
"frontMatter.config.dynamicFilePath": "[[workspace]]/frontmatter.config.js",
"frontMatter.site.baseURL": "https://kollitsch.dev",
"frontMatter.content.pageFolders": []
} |
Hi @davidsneighbour, at the moment, the updates to your config are only applied to the It would be more of an enhancement to support this, as it requires finding the location of the config file and updating it. |
I am ok with that, but the "bug" is, that IF I have a split configuration, then that popup goes into my Is this: {
"frontMatter.content.pageFolders": []
} ignored (or merged) if I have a |
I know 😄 |
I've been implementing a change where there is a check on setting updates. When the to-be-updated setting exists in an extended config (from The output will tell you the setting name and the value that it was trying to update. What do you think? |
I have a folder that ceased to exist, configured in
.frontmatter/config/content/pagefolders/components.json
.FrontMatter complains that it does not exist (good) and offers to remove it or create it (good):
Clicking on "Remove Folder" results in a small notice for <1s about removing the setup, but the file is not modified or deleted.
.frontmatter/database/mediaDB.json
seems to have been changed, but I am not sure if that is connected to this issue.PS: the popup shows a different path because I tried some setup related to #787. The path is correctly displayed in the popup.
The text was updated successfully, but these errors were encountered: