In frontmatter.json, it looks like the original simple model for i18n and pageFolder is getting transformed internally and then (perhaps unintentionally?) getting persisted to back to frontmatter.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.
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.
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.
<!-- github-comment-id:1972705278 -->
Tested and passed. I added a temporary snippet to ensure frontmatter.json was serialised and the result was ok.
Thanks again. Glad we caught this one before it broke too many frontmatter.json files in the wild.
Tested and passed. I added a temporary snippet to ensure `frontmatter.json` was serialised and the result was ok.
Thanks again. Glad we caught this one before it broke too many `frontmatter.json` files in the wild.
<!-- github-comment-id:1972787295 -->
@tohagan a fix will be included to revert the setting to the original state: https://github.com/estruyf/vscode-front-matter/blob/6f6015cf834765bd22798c310b625c03d5fe4f28/src/helpers/Extension.ts#L247-L270
<!-- github-comment-id:1972837149 -->
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
In
frontmatter.json, it looks like the original simple model fori18nandpageFolderis getting transformed internally and then (perhaps unintentionally?) getting persisted to back tofrontmatter.json.IMHO, this complicates and duplicates information in the
frontmatter.jsonmodel. 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 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
frontmatter.jsonwas serialised and the result was ok.Thanks again. Glad we caught this one before it broke too many
frontmatter.jsonfiles in the wild.Release notes might want to have repair instructions.
@tohagan a fix will be included to revert the setting to the original state: https://github.com/estruyf/vscode-front-matter/blob/6f6015cf834765bd22798c310b625c03d5fe4f28/src/helpers/Extension.ts#L247-L270