When I make changes to a file through the UI or by updating the date by saving, empty front-matter fields are removed. I'm assuming this is a bug, as the CMS shouldn't delete existing data except as replacing existing values through the UI.
If I manually add a value to an empty field in the editor, that field remains after the save.
EDIT: The behavior went back as expected after uninstalling the extension. My assumption is that changes made to the parsing caused this behavior.
Using v6.1.1869350
When I make changes to a file through the UI or by updating the date by saving, empty front-matter fields are removed. I'm assuming this is a bug, as the CMS shouldn't delete existing data except as replacing existing values through the UI.
If I manually add a value to an empty field in the editor, that field remains after the save.
EDIT: The behavior went back as expected after uninstalling the extension. My assumption is that changes made to the parsing caused this behavior.
<!-- github-sync-id:1145962967 -->
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.
Using v6.1.1869350
When I make changes to a file through the UI or by updating the date by saving, empty front-matter fields are removed. I'm assuming this is a bug, as the CMS shouldn't delete existing data except as replacing existing values through the UI.
If I manually add a value to an empty field in the editor, that field remains after the save.
EDIT: The behavior went back as expected after uninstalling the extension. My assumption is that changes made to the parsing caused this behavior.
Thanks, @johnfuller should be fixed. This was related to issue #242. Good catch!