electrodb - npm Package Versions

[1.10.1] - 2022-06-30

Fixed

• Exported additional types

[1.10.0] - 2022-06-29

Fixed

• TypeScript 4.7 introduced changes that caused type inference issues with the Entity, Service, and exposed types. A re-vamp of some typing was done to rectify these issues, new tests and existing tests were made work with the latest versions of TypeScript and tsd.

Changed

• Project now is more deliberate about the types exposed via the package. This is because I have moved away from a single type definition file (which by default exports all types). If you had a dependency on a type that used to be exposed, open a ticket and I can expose it. In the future exposed types will be the only types officially supported by semver.

[1.9.0] - 2022-06-18

Added

• Add new batchGet query option, preserveBatchOrder, which will ensure the order returned by a batchGet will be the same as the order provided. [read more]

[1.8.4] - 2022-05-18

Changed

• Removing validation that an attribute used for one index cannot be used by another. ElectroDB will now simply validate that all composite attributes associated with an indexed field are identical, and that a field is not used as both a PK and SK in separate indexes. This change allows for LSIs to be used with ElectroDB

[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]