As noted in #102, AnalyzeExpense API may sometimes not return a geometry/bounding box for expense field detections where the text is empty "". Fixed the underlying API model and the TRP class to reflect this possibility. Updated sample response JSONs used for tests, and updated build environment NodeJS ver to most current LTS.
Issue #, if available: #102
Description of changes:
(In JavaScript/TS version of the library):
Fix TextractExpense (and underlying API data types) to correctly handle cases where Amazon Textract AnalyzeExpense may not return a geometry for a detected field (typically where the detected text is empty).
Update tests to use more recent sample Amazon Textract response JSONs and explicitly test the missing AnalyzeExpense geometries.
Update build environment NodeJS to current LTS
Open TODOs:
Seek user confirmation that release 0.2.1-alpha.1 correctly fixes issue #102
Release mainline version 0.2.1 (update package.json, package-lock.json, CHANGELOG)
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
athewsey
commented
1 year ago
As noted in #102, AnalyzeExpense API may sometimes not return a geometry/bounding box for expense field detections where the text is empty "". Fixed the underlying API model and the TRP class to reflect this possibility. Updated sample response JSONs used for tests, and updated build environment NodeJS ver to most current LTS.
Issue #, if available: #102
Description of changes:
(In JavaScript/TS version of the library):
TextractExpense(and underlying API data types) to correctly handle cases where Amazon Textract AnalyzeExpense may not return a geometry for a detected field (typically where the detected text is empty).Open TODOs:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.