|
1 | 1 | ## 1.0.0 |
2 | 2 |
|
| 3 | +## 1.6.0 |
| 4 | + |
| 5 | +### Minor Changes |
| 6 | + |
| 7 | +- 849d8eb: Migrate onto the structurer and upgrade the SDK |
| 8 | + |
| 9 | + The block now follows the canonical `block-tools structure` layout on |
| 10 | + block-tools 2.14.3, with the SDK bumped to model/ui-vue 1.83.x, workflow-tengo |
| 11 | + 6.8.3, tengo-builder 4.0.23 and test 1.83.2. |
| 12 | + |
| 13 | + Two changes are visible outside the block: |
| 14 | + |
| 15 | + - **A new `kind` component** declares the block's identity and its init-params |
| 16 | + contract. `BlockParams` is `{ inputAnchor?: PlRef }`, so a project template |
| 17 | + can seed a new instance with the dataset to analyse. Every other field in the |
| 18 | + block's data is view state and still defaults. |
| 19 | + - **`block` is now a slim facade.** It publishes with no dependencies, bundles |
| 20 | + the whole block into `dist/` plus `block-pack/`, and exports |
| 21 | + `SequencePropertiesBlockPointer` for consumers that add the block from code. |
| 22 | + |
| 23 | + `@platforma-sdk/ui-vue` is on 1.83.3, which publishes the component |
| 24 | + declaration files its own type entry re-exports again — 1.83.1 had dropped |
| 25 | + them and broke the facade build. |
| 26 | + |
| 27 | +- c340cab: Read the input's declared `pl7.app/modality` instead of guessing from the run-id key |
| 28 | + |
| 29 | + `synthetic-repertoire-profiler` runs one pipeline over both antibody/TCR parents and designed |
| 30 | + libraries, and everything it emits sits on the modality-neutral `pl7.app/variantKey` axis. It |
| 31 | + keeps the same `pl7.app/repertoire/extractionRunId` key in both cases, so a VDJ run used to be |
| 32 | + read as amplicon and scanned as one whole sequence — its FR1–FR4 regions, CDR3 included, were |
| 33 | + never used. |
| 34 | + |
| 35 | + The profiler now declares which kind of repertoire it produced in the entity-axis domain, and |
| 36 | + this block reads that declaration: `vdj` takes the per-region antibody/TCR path, `amplicon` the |
| 37 | + whole-sequence path. A VDJ run therefore gets CDR3 charge and hydrophobicity, and full-chain |
| 38 | + properties, the same as MiXCR input does. |
| 39 | + |
| 40 | + Datasets with no declaration keep the previous behaviour exactly, so projects made before the |
| 41 | + declaration landed are unaffected. |
| 42 | + |
| 43 | + Two smaller things follow from it. A declared VDJ input carries no receptor — the profiler has |
| 44 | + none to emit, since germline auto-detect builds its reference from the user's own parent |
| 45 | + sequences — so the "receptor not detected" notice no longer tells those users to pick a MiXCR |
| 46 | + preset they never used; it says the labels defaulted to the antibody convention and that only |
| 47 | + labels are affected. And modality detection moved into its own workflow module so it could be |
| 48 | + unit-tested; `pnpm test` on the workflow package now runs those tests. |
| 49 | + |
3 | 50 | ## 1.5.2 |
4 | 51 |
|
5 | 52 | ### Patch Changes |
|
0 commit comments