The updateProductVariant mutation does not change the updatedAt field.

[skid]

Describe the bug
The updatedAt field of a ProductVariant remains the same (equal to the createdAt) after updates.

To Reproduce

1. Change the price of a product variant in the Admin UI and click update
2. Check the database record for that PV

Expected behavior
The ProductVariant should have the updatedAt field set to its latest update date.
Additionally, this object should be passed to the event bus (for instance, if the updatedAt is a database timestamp, we should make sure that the actual in-memory entity instance reflects the new updatedAt date).

Environment (please complete the following information):

• @vendure/core version: 1.2.0
• Nodejs version 14
• Database (mysql/postgres etc): 13

[michaelbromley]

Thanks for the report. This was really tricky to track down, but it turned out to be a bug in the translateDeep helper function which was copying over the "createdAt" and "updatedAt" values from the translation entity to the ProductVariant itself.

It's also worth noting that for all entities, the "updatedAt" only changes when its own properties are changed, not that of any related entities. Perhaps you already knew this but it might not be obvious that e.g. updating a variant's price or name will not change the "updatedAt" value, since it is the "ProductVariantPrice" and "ProductVariantTranslation" entities that are actually being updated respectively.