electrodb - npm Package Versions

[1.8.3] - 2022-05-14

Changed

• Removing validation that requires at least one attribute to be provided in a PK composite. This opens the door to static PKs if the user so chooses

[1.8.2] - 2022-05-13

Fixed

• Issue impacting the successful propagation loggers and listeners from a Service definition to Entity children

[1.8.1] - 2022-03-29

Fixed

• Solidifying default application methodology: default values for nested properties will be applied up until an undefined default occurs or default callback returns undefined

[1.8.0] - 2022-03-28

Added

• Expected typings for the injected v2 client now include methods for transactWrite and transactGet

Changed

• Map attributes will now always resolve to least an empty object on a create and put methods (instead of just the root map)
• In the past, default values for property attributes on maps only resolves when a user provided an object to place the values on. Now default values within maps attributes will now always resolve onto the object on create and put methods.

[1.7.2] - 2022-03-27

Fixed

• Fixed issue#111, update method specific query option typing no longer lost when using a where method in a query chain
• Fixing incorrect typing for exposed UpdateEntityItem type. Exported type was missing composite key attributes

[1.7.1] - 2022-03-19

Added

• Adding support for the v3 DynamoDBClient. This change also brings in a new ElectroDB dependency @aws-sdk/lib-dynamodb. [read more]

[1.7.0] - 2022-03-13

Added

• New feature: "Listeners". Listeners open the door to some really cool tooling that was not possible because of how ElectroDB augments raw DynamoDB responses and did not provide easy access to raw DynamoDB parameters. [read more]

[1.6.3] - 2022-02-22

Added

• Add data update operation ifNotExists to allow for use of the UpdateExpression function "if_not_exists()".

[1.6.2] - 2022-01-27

Changed

• The methods create, patch, and remove will now refer to primary table keys through parameters via ExpressionAttributeNames when using attribute_exists()/attribute_not_exists() DynamoDB conditions. Prior to this they were referenced directly which would fail in cases where key names include illegal characters. Parameter implementation change only, non-breaking.

[1.6.1] - 2021-12-05

Fixed

• In some cases the find() and match() methods would incorrectly select an index without a complete partition key. This would result in validation exceptions preventing the user from querying if an index definition and provided attribute object aligned improperly. This was fixed and a slightly more robust mechanism for ranking indexes was made.