`dynoexpr` should handle `null` value type

[mikestopcontinues]

`dynoexpr` should handle `null` value type

[ruicsh]

hey, can you give an example? how would the NULL be specified? as a string?

[mikestopcontinues]

Oh, I'm sorry, I was just referring to the way it's specified in the API (data value NULL like S, N, etc), to clarify that it's a supported DDB feature.

As far as usage, I'd really like to just use null as usual, but right now I'm getting a type error. The one conflict I know for sure is DynoexprInputValue. But I've been trying to hit any other locations as I build out the model/api for a new project. I definitely can use null (at least in update ops), but beyond that, I haven't found any other snags. Sorry again for the muddy report. :)

[mikestopcontinues]

Hey, I was just doing some db work and hit on this issue again. Does it require deeper research on your end? Can I submit a PR?

[ruicsh]

hey, of course, please do... sorry, been busy with work and other side hustles :)

[ruicsh]

🎉 This issue has been resolved in version 2.7.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀