@pixelverse/strichjs-sdk 1.5.1 → 1.5.3

package/CHANGELOG.md

@@ -2,6 +2,34 @@
 
 The structure of this file follows the recommendations from: https://keepachangelog.com/en/1.1.0/
 
+## [1.5.3] - 2024-10-07
+
+### Added
+
+- Support optional Modulo 43 checksum for the Code 39 symbology. Setting the new symbology parameter `checksumMode` to `1` (validate) or `2` (validate and transmit) will expect a check digit. Please note that setting the parameter to `1` or `2` will lead to Code 39 barcodes that lack a valid check digit to be no longer readable.
+- Support optional Modulo 16 checksum for the Codabar symbology. Please refer to the new `checksumMode` symbology parameter for details.
+
+### Fixed
+
+- Removed overly aggressive pruning of candidates introduced in 1.5.2 that caused performance regressions in certain scenarios.
+
+## [1.5.2] - 2024-09-18
+
+### Added
+
+- Add a utility method `StrichSDK.getCameraPermissionState()` that returns the current state of the camera permission: `granted`, `denied`, `prompt` or `unknown`. It relies on the Permissions API which is supported by all major browsers except Firefox. Invoking the method on a browser that does not support the Permissions API will return `unknown`.
+
+### Changed
+
+- If all symbologies are enabled by omitting or specifying an empty `symbologies` array in the configuration, an error message is now logged to the browser console using WARN log level. Previously this was logged by the WebAssembly engine and logged using the normal log level. This change has no impact on customers, and we maintain that logging this state as a warning makes sense, as it indicates a misconfiguration of the SDK.
+
+### Fixed
+
+- Further decreased EAN/UPC barcode misread rates by performing additional checks on the barcode structure.
+- Fixed lower recognition rates due to too aggressive quiet zone checks.
+- Some error messages that were created due to malformed JSON configuration were not propagated from the WebAssembly engine to the `detailMessage` of the `SdkError`.
+- Fixed a rare issue where initializing a `BarcodeReader` with a bad JSON configuration prevented further attempts at initializing it with a correct one.
+
 ## [1.5.1] - 2024-08-26
 
 ### Added