feat(empty-strings): drop empty string strictness to allow new empty string feature

[hookercookerman]

What

• String Mapper now allows empty strings

Why

• Dynamodb has added support for empty strings, this can be vey helpful on updates where you could be looking for deletions and defaults.

[michaelwittwer]

@hookercookerman thanks for the contribution, this is awesome. Will try to bring back the PR as soon as possible. (probably start of next week). Reach out if it is really urgent on your side.

[michaelwittwer]

@hookercookerman could you resolve the one minor issue commented by @simonmumenthaler then this is ready to come back to the master

[hookercookerman]

@michaellieberherr will do I should have time tomorrow BTW this pr is not ready as it does not cater for stringFromDb when empty string which can hamper mappings when empty string; classic empty string as falsey.

[hookercookerman]

@michaelwittwer soz for delay but updated, cheers

this change introduces non backwards compatible changes, so this needs to be a breaking change

[michaelwittwer]

this change introduces non backwards compatible changes, so this needs to be a breaking change.

can you change your commit message as follows:

feat(empty-strings): allow empty string toDb and from
BREAKING CHANGE: empty strings are now valid dynamoDB values (see https://aws.amazon.com/about-aws/whats-new/2020/05/amazon-dynamodb-now-supports-empty-values-for-non-key-string-and-binary-attributes-in-dynamodb-tables/ for official statement) and thus they are mapped to and from db.

then we are finally ready to bring this back.

[github-actions]

🎉 This PR is included in version 6.0.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀