electrodb - npm Package Versions

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

[2.9.1]

Fixed

• Version 2.9.0 was accidentally published without the dependency @aws-sdk/lib-dynamodb

[2.9.0]

Added

• Addresses Issue #277 Introduces new composite() method for update and patch operations. The composite method is used to help electrodb complete and format keys when updating a subset of the key's composite attributes. Prior to this update, updating a key partially resulted in an invalid query error, which caused difficulties when some composite attributes were flagged as readOnly. [read more]
• Adds more deliberate collection validation to ensure entity compatibility. This will allow for indexes defined with "template" be used with collections. This also might cause some existing implementations to now throw on service instantiation, however that would mean these services were never valid to begin with.

[2.8.2] - 2023-08-19

Fixed

• Fixes bug reported via Issue #281: ElectroDB failed to use an attribute's field name when it was updated via watch.
• Fixes bug reported via Issue #229: ElectroDB would generate empty string keys on item creating. This would occur only in cases where a key's field name matched an attribute's field name.

Changed

• Relaxes validation surrounding the use of composite attributes appearing as composite attributes in both the partition and sort key for the same index. Reported in Issue#265, validation surrounding this pattern have been relaxed to only throw when a composite attribute in both the pk and sk AND the sk contains greater than one composite attribute. This constraint is critical for ElectroDB to reliably generate/format sort key values.

[2.8.1] - 2023-08-06

Fixed

• Fixes bug with creating sets when client is provided or changed after initial Entity construction

[2.8.0] - 2023-08-06

Adds

• Adds new cast option for indexes to allow users to cast index values to a different type than their composite attribute. This change comers from a user requested feature and addresses issue #237

Fixed

• Fixed edge case when model defines an index without composites while using the template syntax that prevented ignoreOwnership from correctly gating return records

[2.7.2] - 2023-07-03

Fixed

• Fixed bug reported via Issue #271: Root map object with required flag would not set empty object even when it was provided.