electrodb - npm Package Versions

[1.3.0] - 2021-08-09

Added

• New Attribute types map, list, set. [read more]
• New Query Options, and support for, ReturnValues as requested in Issue#71. [read more]
• New type definitions for recently released update methods append, add, subtract, data, remove, and delete. [read more]

Changed

• Attributes that have been flagged as required are now not possible to be removed (using the update method remove()) from a stored Item. This was an oversight from the last release.
• Attributes that have been flagged as hidden now skips invoking that attribute's getter method.

Fixed

• Issues that prevented the nesting of update value() operation.
• TypeScript type definitions for get() method now incorporate potential for null response.
• Type definitions for value() and name() where clause operations.

[1.2.0] - 2021-07-31

Added

• Added new update methods append, add, subtract, data, remove, delete, and data for improved support of all DynamoDB update methods. [read more]

Changed

• The property names of ExpressionAttributeValues underwent some change in this release due to the addition of new update operations. This is not a breaking change but if you have tests to match on the exact params returned from ElectroDB these will likely break. [read more]

[1.1.1] - 2021-07-07

Added

• Added new syntax for Attribute Property watch to trigger whenever any attribute is updated/retrieved. [read more]

Changed

• The Attribute Property readOnly is now enforced before watch properties are evaluated. This allows properties that use the Attribute Property watch to deliberately circumnavigate readOnly enforcement. [read more]

[1.1.0] - 2021-07-07

Added

• Expanding "collection" concept to include sub-collections. Sub-collections will allow for more precise cross-entity queries to be modeled. [read more]

Fixed

• Addressed edge-case when modeling sparse indexes that would leave unable to be queried via secondary index. [read more]

[1.0.0] - 2021-06-27

Added

• new .match() method to replace original Find method functionality. [read more]
• New template property on Model for building custom composite key templates. The template property also brings forward a new syntax similar to template literal syntax. [read more]
• New custom composite key syntax using the template property. [read more]
• Numeric table keys now possible. Before PK and SK values could only be strings, Numeric Keys are now supported through the templates index property. [read more]

Changed

• Rename of facets property on Model to composite for arrays and template for string templates. [read more]
• Get method now returns null when value is not found. Prior functionality returned an empty object. [read more]
• Strict enforcement of all SK composite attributes being present when performing .get(), .put(), .create(), .delete(), .remove(), .update(), .patch() operations.
• Find method now does not add filters for values supplied, Find now only identifies an Index (if possible) and fulfills the Composite Attributes of that Index (if possible). [read more]
• Query Option lastEvaluatedKeyRaw when used with pagination replaced Query Option pager with option values: "raw", "item", "named". Default set to "named". [read more]
• Query Option lastEvaluatedKeyRaw when used with bulk operations replaced Query Option unprocessed with option values: "raw", "item". Default set to "item". [read more]

Deprecated

• Removing facets property from documentation, examples, and TypeScript typing. Replaced with composite property for arrays and template for string templates. [read more]
• Fully deprecated custom facet string format. Facet strings defined attributes with a prefixed : as in :storeId would resolve to storeId. This has been replaced by the template syntax, surrounding the attribute with ${...}. [read more]