electrodb - npm Package Versions

[2.10.7] - 2023-11-09

Fixed

• Fixes latency issue introduced in 2.10.4 affecting all queries discovered and brought forward by Ross Gerbasi. Thank you, Ross Gerbasi!

[2.10.6] - 2023-11-04

Fixed

• Addresses Issue #321, fixing expression attribute name and value formatting to remove non-alphanumeric and underscore characters.

[2.10.5] - 2023-11-03

Fixed

• Addresses bug in patch and update methods that caused key composite attributes to be set with their attribute name not their "field" name. This would impact users who both use the update method to create new items and use alternative field name definitions for their composite keys. All other users would likely be silently impacted by this issue.

[2.10.4] - 2023-10-26

NOTE: This version is deprecated, this version introduced code that significantly increased latency. That code was fixed in 2.10.7

Added

• Adds cause property to ElectroError, currently populated when error originates from the AWS Client, to help with error triage. This also adds the ability to provide an error type to ElectroError<Error> to type the error located on cause.

[2.10.3]

Fixed

• Addresses edge case that filtered valid items when item lacked entity identifiers (created outside ElectroDB) when keys (pk or sk) were numeric.

[2.10.2]

Fixed

• Addresses Issue #308 and Issue #228

[2.10.1]

Added

• Transact upsert now supports add, subtract, append, set, and ifNotExists operations. Addresses Issue #301.

[2.10.0]

Added

• The upsert method now supports add, subtract, append, set, and ifNotExists operations. Addresses Issue #286.
• The add and subtract operations provided to the data callback operation with update and patch methods now supports a third parameter for supply a defaultValue. Addresses Issue #297.
• A condition expression operation called field that allows for references to raw field names as they exist in the table. This can be used with escape and value to create custom filter expressions.

[2.9.3]

Revert

• Reverts change in 2.9.2. The composite() method no longer allows for attribute_not_exists().

Fixed

• Composite attributes that used the attribute option watch, and were not provided to the create or put methods, were not property applied to their composite keys. This addresses the issue brought forward in discussion #292.

[2.9.2]

Changed

• The composite() method for update and patch now adds a condition expression that allows for cases where the composite attribute doesn't exist. Prior to this change the condition used a strict equals check on the attribute value (e.g. #prop1 = :prop1). This change now revises that expression to (#prop1 = :prop1 OR attribute_not_exists(#prop1)).