Closed Moyf closed 1 month ago
You're right. When using the date or datetime type in Web Clipper we should not use quotes to match the Obsidian app formatting. This change will be in the next version.
Will be fixed in 0.6.0
Will be fixed in 0.6.0
Could it be possible to not adding double quotes symbol for other properties?
Because when I change the property in "Note property view" (the core plugin), it would automatically remove the quotes anyway:
(Tested in the Sandbox vault and it seems that it's the default behavior 🤔)
And (v0.6.1) it seems that no matter what format I set, the string of datetime would always be :
The date format is inconsistent with all my other notes (which causes issues with Dataview processing), and I would prefer to have complete control over the format.
Well you can set your field as a string type, the it will be passed through as is
Well you can set your field as a string type, the it will be passed through as is
Then the issue of "double quotes" would arise again. 😂
Well you can set your field as a string type, the it will be passed through as is
Then the issue of "double quotes" would arise again. 😂
I set the type to Text
, is it correct?
( How can I get rid of double quotes ?
Okay I see the issue. This will be fixed in the next version you will be able to use date
and datetime
types with custom date formats.
Okay I see the issue. This will be fixed in the next version you will be able to use
date
anddatetime
types with custom date formats.
Great! Thank you!
In addition, I would like to understand whether wrapping text property in double quotes is a Markdown syntax rule for YAML? I am a bit confused as to why Obsidian natively removes these double quotes.
It seems that all the properties added by this extension would be
"xxx"
(surrounded by the double quotes) However, it seems that the 'datatime' doesn't have these quotes?If I change the datatime in Obsidian, the Frontmatter would change from:
to:
Is there any setting for this quotes format?