Commit tinylog entries
This commit is contained in:
parent
76f191696d
commit
b92108489f
1 changed files with 6 additions and 4 deletions
|
@ -4,10 +4,10 @@ Meta(
|
||||||
published: Some(Time(
|
published: Some(Time(
|
||||||
year: 2023,
|
year: 2023,
|
||||||
month: 6,
|
month: 6,
|
||||||
day: 7,
|
day: 10,
|
||||||
hour: 20,
|
hour: 13,
|
||||||
minute: 36,
|
minute: 55,
|
||||||
second: 36,
|
second: 59,
|
||||||
)),
|
)),
|
||||||
tags: [
|
tags: [
|
||||||
"tinylog",
|
"tinylog",
|
||||||
|
@ -18,6 +18,8 @@ Some shorter thoughts and updates that might not warrant a full gemlog entry. I'
|
||||||
|
|
||||||
=> .. Home
|
=> .. Home
|
||||||
|
|
||||||
|
## 2023-06-10 13:55 UTC
|
||||||
|
The latest Dory commits center around an iso-8601 time implementation, which is the format that `timestamp` lines are supposed to use in messages. The spec is of course a little ambiguous, and iso8601 allows dates in one of three formats, with the further distinction that there is both a `basic` formatting and an `extended` formatting, where the difference is the appearance of separators between the fields. I've decided for expediency to only implement `calendar` style dates, which is the traditional yyyy-mm--dd format that we're all used to seeing.
|
||||||
## 2023-06-07 20:36 UTC
|
## 2023-06-07 20:36 UTC
|
||||||
Today, after finishing a blog post, I wrote a parser to convert a `&str` to the `Message` struct in Dory. I also added a lot more test coverage, which revealed a few issues to fix.
|
Today, after finishing a blog post, I wrote a parser to convert a `&str` to the `Message` struct in Dory. I also added a lot more test coverage, which revealed a few issues to fix.
|
||||||
## 2023-06-06 18:12 UTC
|
## 2023-06-06 18:12 UTC
|
||||||
|
|
Loading…
Add table
Reference in a new issue