@uipath/du-utils 1.0.0-rc.2 → 1.0.0-rc.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,20 @@ All notable consumer-facing changes to `@uipath/du-utils` are documented in this
|
|
|
4
4
|
follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the package follows
|
|
5
5
|
[Semantic Versioning](https://semver.org/).
|
|
6
6
|
|
|
7
|
+
## [1.0.0-rc.3] - 2026-10-01
|
|
8
|
+
|
|
9
|
+
Third release candidate for `1.0.0`. The loader functions and their options are unchanged. One
|
|
10
|
+
event payload changed: read **Changed** before upgrading.
|
|
11
|
+
|
|
12
|
+
> 🚀 This is a **release candidate**. Please report any issues before the stable release.
|
|
13
|
+
|
|
14
|
+
### Changed
|
|
15
|
+
|
|
16
|
+
- **Breaking:** the `actionCenterTaskCompleteWithResult` detail is now
|
|
17
|
+
`{ taskId, processedDocument }` instead of `{ taskId, validatedExtractionResult }`. Complete the
|
|
18
|
+
task with `processedDocument` as its `data`, verbatim. Its shape belongs to the node downstream,
|
|
19
|
+
so pass it through without inspecting it.
|
|
20
|
+
|
|
7
21
|
## [1.0.0-rc.2] - 2026-09-28
|
|
8
22
|
|
|
9
23
|
Second release candidate for `1.0.0`. The loader functions and their options are unchanged. The
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@uipath/du-utils",
|
|
3
|
-
"version": "1.0.0-rc.
|
|
3
|
+
"version": "1.0.0-rc.3",
|
|
4
4
|
"description": "Framework-agnostic loaders and TypeScript contracts for embedding the UiPath Document Understanding web components (Validation Station and Classification Station).",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"uipath",
|
|
@@ -382,16 +382,18 @@ export interface IValidationStationWcEventMap extends IVsWcSharedEventMap {
|
|
|
382
382
|
* Fires alongside `actionCenterTaskComplete` when the document came from a `processedDocument`,
|
|
383
383
|
* carrying the reviewer's result as well as the task id.
|
|
384
384
|
*
|
|
385
|
-
* Complete the task with
|
|
386
|
-
* task's data as its output, so a completion without it produces nothing.
|
|
387
|
-
*
|
|
385
|
+
* Complete the task with `processedDocument` as its `data`, verbatim: a downstream node reads
|
|
386
|
+
* the completed task's data as its output, so a completion without it produces nothing. Its
|
|
387
|
+
* shape belongs to the node downstream, not to this contract, so pass it through without
|
|
388
|
+
* inspecting it — today it is the `processedDocument` the station was given, with its `result`
|
|
389
|
+
* replaced by the reviewer's.
|
|
388
390
|
*
|
|
389
391
|
* A classic `contentValidationData` document fires only `actionCenterTaskComplete`, since it
|
|
390
392
|
* persists its own result and the task needs no data.
|
|
391
393
|
*/
|
|
392
394
|
actionCenterTaskCompleteWithResult: {
|
|
393
395
|
taskId: number;
|
|
394
|
-
|
|
396
|
+
processedDocument: unknown;
|
|
395
397
|
};
|
|
396
398
|
/** Fires when the Action Center task has been reported as exception. Detail is the task ID. */
|
|
397
399
|
actionCenterTaskReportAsException: number;
|