🚀 Feature: Don't change $updatedAt

[step135]

🔖 Feature description

There are some cases, for example when admin corrects some field in document or adds meta data, when $updatedAt shouldn't change. But there is no possibility to suppress the trigger.

🎤 Pitch

$updatedAt is not required to be changed every time when any document receives updates.

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[stnguyen90]

@step135, thanks for raising this issue! 🙏🏼 We have discussed being able to set $createdAt and $updatedAt manually recently, especially since Migrations doesn't preserve these values.

[FranciscoKloganB]

I've personally treated $createdAt and $updatedAt and most attributes prefixed by $ as Appwrite owned. I use my own createdAt, updatedAt and deletedAt attributes, the only $attr I am using from is $id to avoid referencing issues. It is not ideal, but it works for me.