test(tests): R4.1a frozen TS scanner (N-1 PDF reader) and synthetic L/CAP reports
This commit is contained in:
1 parent
eff54059f4
commit
7ecbee9aae
10 files changed
+32616
No files matched your search
@@ -0,0 +1,26 @@
|
||||
# Frozen TypeScript scanner (O11)
|
||||
|
||||
Never edited; the permanent N-1 PDF reader (R4 plan B.2.2).
|
||||
|
||||
The byte-scan attachment reader of the R3 build and release 0.2.0, copied
|
||||
verbatim from `packages/pdf/src` at commit
|
||||
`eff54059f45fb24a2255f0c099d4585021ef58eb` (branch `feature/rust-r4-pdf-core`,
|
||||
R4.1). Every R4 PDF must stay readable by it, and an R4 PDF whose EmbeddedFile
|
||||
stream was removed must answer `attachment_stripped` through it: a rollback to
|
||||
the R3 build then reads what R4 wrote. `tests/n-1.scanner.test.ts` proves it
|
||||
reads the frozen fixture PDFs.
|
||||
|
||||
| Copy | Source | sha256 |
|
||||
| ----------------------- | ---------------------------------------- | ------------------------------------------------------------------ |
|
||||
| `errors.ts` | `packages/pdf/src/errors.ts` | `06c2f518190f96f969539c4298a222e6f6fbae6a71493294d480d7ea3381c2b2` |
|
||||
| `attachment/scan.ts` | `packages/pdf/src/attachment/scan.ts` | `82c1c0ef51f29191c8a5238f39ed21222a890658721da7d0c964f2053e7b9894` |
|
||||
| `attachment/inflate.ts` | `packages/pdf/src/attachment/inflate.ts` | `6a8275a1fe68879d90d49fffcd5203e515f840738ea2083370e831b93beeca10` |
|
||||
| `attachment/read.ts` | `packages/pdf/src/attachment/read.ts` | `d11e93cc143edaeb3a7f07327b85b669839e43e35817625c14dc6aa03659b91f` |
|
||||
|
||||
Changed lines: none. The source tree shape (`errors.ts` beside `attachment/`)
|
||||
is kept, so every import specifier (`../errors`, `./scan`, `./inflate`)
|
||||
resolves unchanged. The four modules import nothing else; `attachment/write.ts`
|
||||
(pdf-lib, export side) is not part of the reader and is not copied.
|
||||
|
||||
`attachment/scan.ts` is not Prettier-clean (line 481, as in its source):
|
||||
never reformat it.
|
||||
Reference in new issue
Block a user