Closed StrollStars closed 1 year ago
Same thing happened to me, I was using a custom metadata within the file template. However, version 1.3 moved all YAML to Front Matter Variables.
I can see how this would be simpler for some users – and can probably guess that some were messing with id:
which affected the sync. However, this throws a wrench at my current workflow in obsidian, since I relied on my custom attributes.
Not sure if this is the same thing or not. I attempted to add a "Reviewed: false" line to the YAML template but it's not using it.
@mwisnefsky Variables available in the template
@mwisnefsky Variables available in the template
Ah - my bad, didn't realize it stripped out YAML that didn't match the predefined ones.
Hey guys, Omnivore plugin 1.4.0 is out.
I hope it will solve all the issues with parsing YAML in the front matter and the sync will continue even if there was a parsing error.
Additionally, now you can create an alias for the metadata in the front matter in the format of metadata::alias
. For example, state::status
will create a metadata status
to represent the state
. The available metadata could be found here.
Screenshot:
Moreover, for users with the need to put hardcoded metadata in the front matter or some other advanced usage, we have added a "front matter template" section under the "Advanced Settings". It will override the "Front matter" if set. Sample template could be found here.
Screenshot:
@sywhb My question has been resolved. Thank you, developers.
Comparing two images, there are 3 synchronous problems: