Recent versions do not run onDefault if dependsOn contains undefined parameter about dynamodb-toolbox HOT 2 CLOSED

Hello @naorpeled
Yes, you're right about the assumption that I only want to write at creation time (the default value). I do not use dependsOn to check for changed property (as for that you could use onUpdate: true and pass all properties to calculate the default), but I do use it as on the keys (e.g. key4) also uses a function to calculate the default based on another property.
I evaluated my code and found out that dependsOn only needs to be used for properties that have a default value generated, in which case I can shorten the dependsOn graph. Thank you for that insight.

from dynamodb-toolbox.

Hey @Jimmy89,
in this case I think that dependsOn is redundant, no?
it's a field that you want to only write on creation and not during updates, right? 🙏

Regarding changing the dependsOn logic to allow checking if at least one property changes also makes sense to me but need to give this more thought.
Probably worth creating additional configuration for that as I wouldn't want to accidentally cause cases where some keys would be malformed (e.g. POSTED-AT_undefined#USER_12345).

from dynamodb-toolbox.