Skip to content

Commit 88c3b9b

Browse files
nekevssjedel1043
andauthored
Update blog/2025-06-15-temporal-impl-1.md
Co-authored-by: José Julián Espina <[email protected]>
1 parent bfb9483 commit 88c3b9b

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

blog/2025-06-15-temporal-impl-1.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -322,11 +322,13 @@ const pd_from_property_bag = Temporal.PlainDate.from({
322322
});
323323
```
324324

325-
It turns out that the above operations is all that needs to be
326-
implemented by `temporal_rs` in order to support a Temporal
327-
implementation, we just need to implement `From<PlainDateTime>`,
328-
`From<ZonedDateTime>`, `FromStr`, and `From<JsObject>` ... oh. Did I
329-
mention `JsObject`, like `JsValue`, is implementation defined as well?
325+
If we look closely to the common usage of the method, it seems like
326+
all that needs to be implemented by `temporal_rs` is:
327+
- `From<PlainDateTime>`: Easy.
328+
- `From<ZonedDateTime>`: Simple.
329+
- `FromStr`: Tricky but can be done.
330+
- `From<JsObject>`: ...
331+
... oh. Did I mention `JsObject`, like `JsValue`, is engine defined as well?
330332

331333
Fortunately, this is where `temporal_rs`'s Partial API comes in.
332334

0 commit comments

Comments
 (0)