electrodb - npm Package Versions

[2.7.1] - 2023-07-03

Fixed

• Upsert now only allies if_not_exists() if the attribute is not a composite attribute in an index.

[2.7.0] - 2023-07-01

Fixed

• Fixes return typing for delete, remove, update and upsert operations. These types were incorrect and did not reflect the real values returned. Instead of breaking the APIs, changing response types to T | null, the new response type is now the Entity's key composite values by default. You can also now use the Execution Option response to get back the item as it exists in the table. This is the closed I could get to a non-breaking change that also fixes the incorrect return typing for these methods.
• Fixes typing for contains where conditions to accept collection element values (e.g., set and list type attributes).
• The exported type UpdateEntityItem was incorrectly typed, it now includes the correct typing as the values that can be passed to the set method

Changed

• Upsert operations now take into consideration readOnly attributes when applying changes. If an attribute is configured as readOnly ElectroDB will apply the property with an if_not_exists set operation to prevent overwriting the existing value if one is set.

[2.6.1] - 2023-06-09

Added

• For queries, ElectroDB now trims the ExclusiveStartKey object to only include the keys associated with the index provided. DynamoDB currently rejects queries when properties not associated with the keys of the queried index are provided on the ExclusiveStartKey. By removing irrelevant properties, ElectroDB offers users more flexibility and opportunities for dynamic querying.

[2.6.0] - 2023-05-22

Added

• Adds new query execution option hydrate. When a GSI uses a KEYS_ONLY projection, the hydrate option will perform the query and then a subsequent batchGet to "hydrate" the results.
• Adds new conversion methods to help transform values between "composite attributes", "keys", and "cursors".
• Adds improved return typing for patch operations. The response type for patch now returns an Entity item when passed the execution options { response: 'all_new' } or { response: 'all_old' }.

Fixed

• A common issue amongst new users, was unexpected errors when using a terminal method twice on a query chain. This would often come up when a user called .params() to log out parameters and then call .go() on the same chain. The fix was to prevent duplicative side effects from occurring on each subsequent terminal method call.
• Fixes typing issue with transactGet api that would type response.data as never when the transaction included more than one element.

[2.5.1] - 2023-03-22

Fixed

• The previous version exported typings directly from the AWS dynamodb client package which, because it was so large, caused the playground to take a massive performance hit. Instead, the library now expose a simplistic version of those types instead.

[2.5.0] - 2023-03-19

Added

• Adds transaction functionality: get and write transactions are now supported in ElectroDB via transact write and transact get methods.

[2.4.2] - 2023-03-03

Fixed

• Restores ignoreOwnership execution option. Addresses Issue #194 which calls out regression with ignoreOwnership. This flag is now appropriately applied to "query", "get", and "scan" operations.

[2.4.1] - 2023-01-20

Fixed

• Recently added createSchema() function would validate but not return the schema object provided

[2.4.0] - 2022-01-19

Added

• Adds the new filter expression methods: size(), type() and escape. Addresses Issue#208 [read more]
• Adds the createSchema() function for helping create and type ElectroDB schemas without instantiating an Entity. Addresses Issue#167. [read more]

[2.3.5] - 2022-12-18

Fixed

• Fixes issue that resulted in provided undefined values from becoming involuntarily set via updates
• Updated documentation links in error message to direct traffic to https://electrodb.dev