You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default behaviour of dynamo-easy filters out all null (or undefined) values before the mapper function toDb is called. So it's not possible to store null as { NULL: true }
--> as soon as we define string | null as type it's necessary to provide the actual type to the decorator since reading the reflection information design:type will return Object.
Another option would be to globally define how to handle null values. But then it's less explicit and I think the default behaviour of not storing null is mostly preferred.
The text was updated successfully, but these errors were encountered:
The default behaviour of dynamo-easy filters out all null (or undefined) values before the mapper function
toDb
is called. So it's not possible to storenull
as{ NULL: true }
It'd be nice to have real null value support.
It could be sth like this:
--> as soon as we define
string | null
as type it's necessary to provide the actual type to the decorator since reading the reflection informationdesign:type
will returnObject
.Another option would be to globally define how to handle null values. But then it's less explicit and I think the default behaviour of not storing null is mostly preferred.
The text was updated successfully, but these errors were encountered: