Availability
Sell-policy layer (stock-managed, backorder, preorder, thresholds) on top of the shared availability contract.
Found by static analysis of the 0.9.0 source. Links that only appear at runtime are not visible here.
Everything availability needs outside the starter set is declared. 1 link into a starter module is not, and every app has it.
Before you enable availability in 0.9.0
1 module its code requires
✓ 0 declared1 not declared, in every app
Every module it requires is already in every starter app.
Already enabled in every starter app: 1 module.
Before you disable availability in 0.9.0
0 modules require it in code
No module requires availability in code.
1 more uses it optionally or for collaboration.
35 calls in this release could not be resolved, so this is not a guarantee.
Required, declared ⚠ Gap: required in code, not in
requires ⚠ Gap into a module every starter app has (lower risk) Optional Collaboration In requires only, not seen in code In every starter appA dot takes its module's area colour. Each side lists the areas in the order of the map.Reads left to right: what uses it → availability → what it needs. Select a module to go to its row.Needs
In every app (1)
| Module | In code | requires | package.json |
|---|---|---|---|
Module: directory | In code: Required · lib | requires: ⚠ Gap in every app | package.json: Same package |
1 place
| |||
Used by
| Module | In code | requires | package.json |
|---|---|---|---|
Module: wms | In code: Collaboration · subscriber | requires: Not declared | package.json: Same package |
1 place
| |||
Facts
Registers in DI (2)
AvailabilityPolicy·packages/core/src/modules/availability/di.ts:61policyResolutionService·packages/core/src/modules/availability/di.ts:62
Entities (1)
AvailabilityPolicy·packages/core/src/modules/availability/data/entities.ts:14