Open simonmumenthaler opened 4 years ago
This is absurd - how can this not be implemented?
I looked into this a bit and found that null was being deliberately excluded from mapping; I've raised a PR to rectify this: https://github.com/shiftcode/dynamo-easy/pull/361
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.