fix: deserialize from str for serde YAML compatibility

[LeoniePhiline]

Summary

Neither serde_yaml nor serde_yml used to be able to deserialize jiff types, due to lack of support for serialization from bytes.

Furthermore, an inconsistency between deserialization and serialization was brought forth in #138, where Serialize implementations instruct the corresponding Serializer to collect &strs, but Deserialize implementations instruct the corresponding Deserializers to provide bytes.

All serialized representations making use of no more than the ASCII character set, which makes the switch to deserializing from &str trivial.

This changeset first adds tests, proving the incompatibility.

Then, it provides a fix by hinting to Deserializers that a &str is expected to be passed to the Visitor next.

Commits

dab4b87 — test: verify serde YAML compatibility

Deserializing jiff types from YAML is not currently possible.

Neither serde_yaml nor its maintained fork serde_yml support deserializing from bytes.

These tests serve in both

• proving the current incompatibility
• verifying the fix in the following commit, which migrates Deserialize implementations to deserializer.deserialize_str.

Related to #148, #138

d69f375 — fix: deserialize from str for serde YAML compatibility

Deserializing jiff types from YAML was previously not possible:

Neither serde_yaml nor its maintained fork serde_yml support deserializing from bytes.

This changset migrates Deserialize implementations to deserializer.deserialize_str, thus providing serde YAML compatibility.

Fixes #138

Related to #148

[LeoniePhiline]

Please note that the failure of ci / wasm32-unknown-uknown (pull_request) is unrelated.

These seem to fail in all cases since October 17th.

[LeoniePhiline]

Timezone lookup fails in cross compilation jobs.

I will switch to UTC.