@beliq/sdk 0.5.0 → 0.5.1
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 +24 -0
- package/dist/index.d.cts +100 -45
- package/dist/index.d.ts +100 -45
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,30 @@
|
|
|
4
4
|
resolves 0.4.x and never reaches 0.5.0. Additive spec syncs ship as patches for
|
|
5
5
|
that reason, and a minor is reserved for a change that needs consumers to opt in.
|
|
6
6
|
|
|
7
|
+
## 0.5.1 - 2026-10-11
|
|
8
|
+
|
|
9
|
+
A patch: the types gain two fields and two error codes. No method changes.
|
|
10
|
+
|
|
11
|
+
- The vendored `openapi.json` is document `0.15.0` of the API, up from
|
|
12
|
+
`0.12.0`.
|
|
13
|
+
- `ValidationResult` gains `verificationBadgeLabel`, the English label of the
|
|
14
|
+
badge in `verificationBadge`. It is display text: print it as it is, and
|
|
15
|
+
compare `verificationBadge` in code. The API sets it only beside the badge,
|
|
16
|
+
so a result with no badge has no label. The `validationResult` of a sealed
|
|
17
|
+
`generate()` is the same type and carries it too.
|
|
18
|
+
- `ValidationResult` gains `pdfInput`, which the API sets when the document
|
|
19
|
+
sent to `validate()` was a PDF: the name of the embedded file the verdict is
|
|
20
|
+
about, how that file was found, how many candidates the PDF holds, and
|
|
21
|
+
`containerChecked: false`, because nothing checked the PDF around it.
|
|
22
|
+
- The error code union gains `CONVERSION_OUTPUT_INVALID` and `PDFA_VIOLATION`.
|
|
23
|
+
`convert()` answers 422 `CONVERSION_OUTPUT_INVALID` when the converted XML
|
|
24
|
+
fails validation: the document is not returned, and the verdict is in
|
|
25
|
+
`err.details.validationResult`. `generate()` answers 422 `PDFA_VIOLATION`
|
|
26
|
+
when veraPDF reports a violation of its PDF/A-3b profile in a ZUGFeRD or
|
|
27
|
+
Factur-X PDF it built: the PDF is not returned, and the failed rules are in
|
|
28
|
+
`err.details.failedRules`. A `switch` over the code that TypeScript checks
|
|
29
|
+
for exhaustiveness needs the two new cases.
|
|
30
|
+
|
|
7
31
|
## 0.5.0 - 2026-10-08
|
|
8
32
|
|
|
9
33
|
A minor, because code that reads a `parse()` result can stop compiling, and a
|