dynamo-easy icon indicating copy to clipboard operation
dynamo-easy copied to clipboard

Support Null Values

Open simonmumenthaler opened this issue 5 years ago • 2 comments

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 }

It'd be nice to have real null value support.

It could be sth like this:

@Property({ nullable: true, type: String })
myProperty: string | null

--> 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.

simonmumenthaler avatar Mar 30 '20 15:03 simonmumenthaler

This is absurd - how can this not be implemented?

dhmw avatar Sep 08 '21 18:09 dhmw

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

dhmw avatar Sep 08 '21 18:09 dhmw