-
-
Notifications
You must be signed in to change notification settings - Fork 78
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: A single multilingual pageFolder is now getting replaced by one per language in frontmatter.json
.
#769
Comments
The settings update was overlooked. Those fields are internal and shouldn't be pushed to the configuration file, and an update to fix it has been pushed. It should be available in the latest beta. Let me know if it got fixed, and I'll release it to the stable version. |
BETA Version: 10.0.8108301 |
Tested and passed. I added a temporary snippet to ensure |
Release notes might want to have repair instructions. |
@tohagan a fix will be included to revert the setting to the original state: vscode-front-matter/src/helpers/Extension.ts Lines 247 to 270 in 6f6015c
|
Describe the bug
In
frontmatter.json
, it looks like the original simple model fori18n
andpageFolder
is getting transformed internally and then (perhaps unintentionally?) getting persisted to back tofrontmatter.json
.IMHO, this complicates and duplicates information in the
frontmatter.json
model. Is that what you intended??Perhaps you need to maintain a computed pageFolder model that maintains the original model as isomorphic in this aspect.
Example
frontmatter.json
... is getting converted into this that's saved in the ...
The text was updated successfully, but these errors were encountered: