Module readiness 

Release readiness of a change order.

A change order releases its revisions atomically, like a release candidate that carries a whole product. Before it goes into review, every revision in it is checked against what it depends on:

• BOM children and item references (drawing, specification, reference) must be released already or be part of the same change order. Otherwise the released assembly could not be reproduced, so this blocks the submit.
• CAD file references come from a heuristic scan of the files (cadrefs). An unreleased item found that way is only a warning.
• A dependency whose revisions are all obsolete is a warning: the design still uses a part that must not be used any more.

Dependencies that are released already were checked when they were released, so one level per revision is enough.

Structs

ChangeAccess

What decides whether a reader sees a change order (see access::change_visible), loaded for the other open changes named in the result.

Dependency

An item a revision of the change order depends on and that is not ready.

Readiness

Result of the readiness check.

Enums

Problem

Why a dependency is not ready for the release.

Constants

OTHER_CHANGE

Text that stands for an open change order the reader may not see.

Functions

check

Checks the dependencies of all revisions of a change order. One query, usable inside the transaction that submits the change.