Bitbybit Docs
    Preparing search index...

    Interface DesignFeatureReport (Models.OCCT)

    What became of one feature in a build: ok, failed with why, suppressed, skipped because a body, profile or face it uses failed or was suppressed first, rebound when a reference lost its faces and, in a build with rebind: "report", took the faces most like its hint, or pending when its outcome must come from the caller, as a script's does (see pending on the result). ms is the time it took and cached says it was reused from an earlier build of the same inputs. A failed feature whose lost references have hints lists, in repairs, the faces most like each; a rebound one lists the faces each took.

    interface DesignFeatureReport {
        id: string;
        type: string;
        status: "ok" | "failed" | "skipped" | "suppressed" | "rebound" | "pending";
        ms: number;
        cached: boolean;
        messages: string[];
        repairs?: DesignRepair[];
    }
    Index

    Properties

    id: string
    type: string
    status: "ok" | "failed" | "skipped" | "suppressed" | "rebound" | "pending"
    ms: number
    cached: boolean
    messages: string[]
    repairs?: DesignRepair[]