Why is updatedAt by default null

[mariusfaber98]

I wanted to use this bundle because it uses DateTimeImmutable instead of DateTime, unlike the Gedmo TimestampableEntity trait.
My question is: why does this bundle set updatedAt to null by default, instead of assigning it the same value as createdAt?
That way, you could easily sort by updatedAt even if a row has only been created and not updated yet.
I believe it would be much more convenient if both updatedAt and createdAt were initialized with the same timestamp.
Is there any specific reason for this behavior that I might be missing?

[cristoforocervino]

Hi @mariusfaber98, thanks for your message.
The library behavior is intended this way in order to distinguish easily when an entity has ever been updated or not!
But your proposal is valid as well! I guess this could become a library option