feat!: convert date to iso instead of number

[rgomezcasas]

Since it's a more standard approach

[TheAlbertDev]

Since it's a more standard approach

Hi @rgomezcasas ,
A question from complete ignorance: why isn't Date used directly as a primitive instead of number/string? And in cases where number/string is used as a primitive, how are value objects that use Date instantiated, since they require a Date in the constructor? (In the toPrimitives/fromPrimitives methods, I could do new Date(number), but I don't see the benefit of adding this extra code .)

On the other hand, I saw there was a breaking change to switch dates to numbers, and now this PR proposes another breaking change to switch to strings. Will you be merging it soon? Just asking to know whether I should wait or move forward while keeping an eye on it.

Merci por vuestro trabajo!

[rgomezcasas]

Thanks, @TheAlbertDev!

Yep, merging it today. 🙌

The reason is that Date is an object, not a scalar value, so you can't have it serialized in JSON or Avro. The only way is to transform it to a Unix timestamp (number) or some string standard (like the ISO one).

We started with the numeric approach, but we realized that we prefer the ISO one since it's easier for humans to read.