You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the time is not the default time, a time trigger is recognized as a date trigger. When tested, this happens when the minutes are less than or equal to 12. At this point it seems that the default @@ is not considered a time trigger, but a separate @ and a date trigger.
For example, @@{01:09} is rendered as @2001-09-01 周六.
Expected Behavior
@@ should be rendered correctly.
Steps to reproduce
Kanban 2.0.48 obsidian 1.5.12
@@{01:09} is rendered as @2001-09-01 周六 @@{14:09} is rendered as @2014-09-01 周一 @@{01:12} is rendered as @2001-12-01 周三 @@{01:12} is rendered as @2001-12-01 周三 @@{01:13} is rendered as 01:13
Strangely enough, when editing, the rendering is correct, but after pressing Enter to end the editing, the rendering is wrong.
The solution I've found so far is to change the time trigger to a completely different symbol than the date trigger, such as %.At this point, everything is normal.
Relevant errors (if available)
No response
Operating system
Windows
The text was updated successfully, but these errors were encountered:
Describe the bug
When the time is not the default time, a time trigger is recognized as a date trigger. When tested, this happens when the minutes are less than or equal to 12. At this point it seems that the default @@ is not considered a time trigger, but a separate @ and a date trigger.
For example,
@@{01:09}
is rendered as@2001-09-01 周六
.Expected Behavior
@@ should be rendered correctly.
Steps to reproduce
Kanban 2.0.48 obsidian 1.5.12
@@{01:09}
is rendered as@2001-09-01 周六
@@{14:09}
is rendered as@2014-09-01 周一
@@{01:12}
is rendered as@2001-12-01 周三
@@{01:12}
is rendered as@2001-12-01 周三
@@{01:13}
is rendered as01:13
Strangely enough, when editing, the rendering is correct, but after pressing Enter to end the editing, the rendering is wrong.
The solution I've found so far is to change the time trigger to a completely different symbol than the date trigger, such as
%
.At this point, everything is normal.Relevant errors (if available)
No response
Operating system
Windows
The text was updated successfully, but these errors were encountered: