export type CasePathResolverInput = {
    /**
     * The IDs of elements (flowNodes/shapes and flows/edges) that are already completed. Non-existing ids will be silently ignored.
     *
     * `Completed` means that the element has been fully executed or definitively cancelled (for BPM engine that supports it and allow instance continuation of cancelled elements).
     * No further user action or automation will update the element.
     */
    completedIds: string[];

    // see see https://github.com/process-analytics/bv-experimental-add-ons/issues/16
    pendingIds?: string[];
};

export type CasePathResolverOutput = {
    /**
     * The `BpmnSemantic` objects retrieved from the model that relate to the ids passed in {@link CasePathResolverInput}.
     */
    provided: {
        completed: {
            shapes: ShapeBpmnSemantic[];
            edges: EdgeBpmnSemantic[];
        };
        // It is not sure that we will let configure pending edges, see https://github.com/process-analytics/bv-experimental-add-ons/issues/16
        pending?: {
            shapes: ShapeBpmnSemantic[];
            edges: EdgeBpmnSemantic[];
        };
    };
    computed: {
        completed: {
            shapes: ShapeBpmnSemantic[];
            edges: EdgeBpmnSemantic[];
        };
        // This may require a more complex type if we want to provide information about why the elements are considered as candidates only
        // We may also split pending and completed elements
        // See https://github.com/process-analytics/bv-experimental-add-ons/issues/24
        candidates: {
            shapes: ShapeBpmnSemantic[];
            edges: EdgeBpmnSemantic[];
        };
    };
};