ExportResult.problems Contract 2.0.0 · package sha256
a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e· generated fromconfigurator-runtime.d.tsbyservices/onsite-scripter/scripts/build-contract-docs.mjs; edit the source, not this file.
Property of ExportResult · stable · since 2.0.0
readonly problems: readonly Problem[];Non-fatal problems of this export: 'asset-failed' (node, url) for each ModelNode the
committed model places (spec section 6.9, ID10) whose asset is unloaded when the export reads
the committed state, so the file lacks it, unless query can't match that node's parts (it
names only a collection, a key, a role other than 'product', or another node); and
'asset-failed' (path the item's address, url, no node) for each kind: 'model' item so
unloaded that query can match: its collection, key, role and meta are tested, a node
never matches it, and a filter on its parts (id, name, slot, kind, tag) keeps it
listed. Each is listed once. Empty when the file holds everything placed (spec section 5.11).
| Rule | Result |
|---|---|
| 1. Neutral name | pass: problems names no product |
| 2. A precedent | not recorded: no ledger row (coverage.json) names this member or its owner |
| 3. Two apps, or labs | pass: 8 apps (fleet cross-check: app-4f16d2f6da, app-510d750508, app-59c5b5751e, app-ceb4eccc72, app-e61a0b42ad, app-f07e9033d9, app-fb16dd1985, app-fc07850558) |
| 4. The cheaper fix first | not recorded per member (Appendix B decides it per need) |